Adding `assertr` to ROpenSci

[tonyfischetti]

• 1. What does this package do? (explain in 50 words or less)
     The assertr package supplies a suite of functions designed to verify assumptions about data early in an analysis pipeline to protect against common data errors and instances of bad data.
• 1. Paste the full DESCRIPTION file inside a code block (bounded by ``` on either end).

Package: assertr
Type: Package
Title: Assertive Programming for R Analysis Pipelines
Version: 1.0.0
Authors@R: person("Tony", "Fischetti", email="tony.fischetti@gmail.com",
  role = c("aut", "cre"))
Maintainer: Tony Fischetti <tony.fischetti@gmail.com>
Description: Provides functionality to assert conditions
    that have to be met so that errors in data used in
    analysis pipelines can fail quickly. Similar to
    'stopifnot()' but more powerful, friendly, and easier
    for use in pipelines.
URL: https://github.com/tonyfischetti/assertr
BugReports: https://github.com/tonyfischetti/assertr/issues
License: MIT + file LICENSE
LazyData: TRUE
Imports:
    dplyr,
    MASS,
    lazyeval
Suggests:
    knitr,
    testthat,
    magrittr
VignetteBuilder: knitr

• 1. URL for the package (the development repository, not a stylized html page)
     https://github.com/tonyfischetti/assertr
• 1. What data source(s) does it work with (if applicable)?
     Any. Mostly in the form of data.frames
• 1. Who is the target audience?
     Anyone who has ever struggled with bad data
• 1. Are there other R packages that accomplish the same thing? If so, what is different about yours?
     The ensurer package attempts to solve the very same problem. To a certain extent, the assertive package also offer some similar capabilities. The difference between assertr and these other packages is the grammar of usage and the way that assertions of different types can be easily combined to express arbitrarily complex assertions in a very readable way.
• 1. Check the box next to each policy below, confirming that you agree. These are mandatory.
• This package does not violate the Terms of Service of any service it interacts with.
• The repository has continuous integration with Travis and/or another service
• The package contains a vignette
• The package contains a reasonably complete readme with devtools install instructions
• The package contains unit tests
• The package only exports functions to the NAMESPACE that are intended for end users
• 1. Do you agree to follow the rOpenSci packaging guidelines? These aren't mandatory, but we strongly suggest you follow them. If you disagree with anything, please explain.
     Yes. All the user-facing functions are in snake case, but the internal functions sometimes use dots (.) as separators. I'm open to changing that. Also, the package doesn't have a code of conduct yet but I think it's a good idea to include.
• Are there any package dependencies not on CRAN?
  No
• Do you intend for this package to go on CRAN?
  It already is
• Does the package have a CRAN accepted license?
  You bet
• Did devtools::check() produce any errors or warnings? If so paste them below.
  No warnings
• 1. Please add explanations below for any exceptions to the above:
• 1. If this is a resubmission following rejection, please explain the change in cirucmstances.

[richfitz]

I have a use case for this and have already looked through the code, so am happy to review if that is useful (at the same time I can't review until the 4th January at the earliest as I will be travelling over the break).

[sckott]

Reviewers: @richfitz @jennybc

[jennybc]

I've been meaning to do one, so I can be the second.

[sckott]

thanks jenny, assigned

[karthik]

@tonyfischetti Excellent! Thanks for submitting! Looking forward to the reviews and adding this to the suite. 😃

[sckott]

@richfitz @jennybc - hey there, it's been 29.0 days, please get your review in soon, thanks 😺

[richfitz]

Sorry - I have been meaning to (and also #25). Next week for both I hope.

[sckott]

cool - (p.s. that comment was your friendly heroku robot https://github.com/ropenscilabs/heythere)

[richfitz]

The descent towards manuscript central begins... 😁

[sckott]

unless you're volunteering to remind everyone manually

[richfitz]

Definitely not! I think it's great. I actually thought it was you, which you could never say for MS central.