Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stop_for_problems #465

Closed
hadley opened this issue Jul 10, 2016 · 1 comment
Closed

stop_for_problems #465

hadley opened this issue Jul 10, 2016 · 1 comment

Comments

@hadley
Copy link
Member

@hadley hadley commented Jul 10, 2016

By analogy to httr::stop_for_status() it would be useful to have a function that threw an error if there were any parsing problems. You'd use this in automated scripts if you wanted to be really sure that the file format hadn't changed

@hadley hadley closed this in 7e87b45 Jul 10, 2016
@hadley
Copy link
Member Author

@hadley hadley commented Jul 10, 2016

@earino - this allows you to be super strict about parsing. I think, combined with the new spec printing behaviour, this should make it easy to rapidly prototype the correct parsing specification and, later, fail-fast if the underlying data changes.

@lock lock bot locked and limited conversation to collaborators Sep 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant