DRAFT: expose s3HTTP error checking without parse_response to e.g allow e.g 404's to be surfaced #377
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm looking to assist with S3-SELECT support.
To do this I've made a repo https://github.com/slodge/aws.s3.select which has header generating and response parsing methods.
However, these methods need code which is currently buried inside parse_response handling under s3HTTP.
This PR tries to open up that error handling... I'm open to other ways to do this.
Current state
R CMD check
does not run - have some tests and some confusing docs to work through yet