You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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.
lockbot
locked and limited conversation to collaborators
Sep 25, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 changedThe text was updated successfully, but these errors were encountered: