Skip to content

Commit

Permalink
Appveyor.
Browse files Browse the repository at this point in the history
  • Loading branch information
kaneplusplus committed Feb 11, 2020
1 parent 0148332 commit a17505e
Show file tree
Hide file tree
Showing 3 changed files with 87 additions and 6 deletions.
16 changes: 13 additions & 3 deletions README.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,20 @@ knitr::opts_chunk$set(
[![Codecov test coverage](https://codecov.io/gh/kaneplusplus/listdown/branch/master/graph/badge.svg)](https://codecov.io/gh/kaneplusplus/listdown?branch=master)
<!-- badges: end -->

The goal of listdown is to programmatically create R Markdown files from
named lists. The package currently supports the creation of workflowr,
pdf, word, html, and slide documents.
## Overview

The listdown package provides functions to programmatically create R Markdown files from
named lists. It is intended for data analysis pipelines where the presentation of the results
is separated from their creation. For this use case, a data processing (or analysis) is performed
and the results are provided in a single named list, organized heirarchically. From the list,
listdown creates a workflowr, pdf, word, or html page. List element names denote sections, subsections,
subsubsection, etc. and the list elements contain the data structure to be presented including
graphs and tables. The goal of the package is not to provide a finished, readable document. It is to provide a document with all tables and visualization that will appear. This serves as a starting point from which a user can organize outputs, describe a study, discuss results, and provide conclusions.

listdown provides a reproducible means for _analytical_ document elements. It is most compatible with
data analysis pipelines where the data format is fixed but the analyses are either being updated,
which may affect _narrative_ elements including the result discussion and conclusion, or where the
experiment is different, which affects all narrative elements.

## Installation

Expand Down
25 changes: 22 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,28 @@ status](https://ci.appveyor.com/api/projects/status/github/kaneplusplus/listdown
coverage](https://codecov.io/gh/kaneplusplus/listdown/branch/master/graph/badge.svg)](https://codecov.io/gh/kaneplusplus/listdown?branch=master)
<!-- badges: end -->

The goal of listdown is to programmatically create R Markdown files from
named lists. The package currently supports the creation of workflowr,
pdf, word, html, and slide documents.
## Overview

The listdown package provides functions to programmatically create R
Markdown files from named lists. It is intended for data analysis
pipelines where the presentation of the results is separated from their
creation. For this use case, a data processing (or analysis) is
performed and the results are provided in a single named list, organized
heirarchically. From the list, listdown creates a workflowr, pdf, word,
or html page. List element names denote sections, subsections,
subsubsection, etc. and the list elements contain the data structure to
be presented including graphs and tables. The goal of the package is not
to provide a finished, readable document. It is to provide a document
with all tables and visualization that will appear. This serves as a
starting point from which a user can organize outputs, describe a study,
discuss results, and provide conclusions.

listdown provides a reproducible means for *analytical* document
elements. It is most compatible with data analysis pipelines where the
data format is fixed but the analyses are either being updated, which
may affect *narrative* elements including the result discussion and
conclusion, or where the experiment is different, which affects all
narrative elements.

## Installation

Expand Down
52 changes: 52 additions & 0 deletions appveyor.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
# DO NOT CHANGE the "init" and "install" sections below

# Download script file from GitHub
init:
ps: |
$ErrorActionPreference = "Stop"
Invoke-WebRequest http://raw.github.com/krlmlr/r-appveyor/master/scripts/appveyor-tool.ps1 -OutFile "..\appveyor-tool.ps1"
Import-Module '..\appveyor-tool.ps1'
install:
ps: Bootstrap

cache:
- C:\RLibrary

environment:
NOT_CRAN: true
# env vars that may need to be set, at least temporarily, from time to time
# see https://github.com/krlmlr/r-appveyor#readme for details
# USE_RTOOLS: true
# R_REMOTES_STANDALONE: true

# Adapt as necessary starting from here

build_script:
- travis-tool.sh install_deps

test_script:
- travis-tool.sh run_tests

on_failure:
- 7z a failure.zip *.Rcheck\*
- appveyor PushArtifact failure.zip

artifacts:
- path: '*.Rcheck\**\*.log'
name: Logs

- path: '*.Rcheck\**\*.out'
name: Logs

- path: '*.Rcheck\**\*.fail'
name: Logs

- path: '*.Rcheck\**\*.Rout'
name: Logs

- path: '\*_*.tar.gz'
name: Bits

- path: '\*_*.zip'
name: Bits

0 comments on commit a17505e

Please sign in to comment.