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
Restructure body parsers to use content type. Add many parsers #584
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Restructure parser list to use the pattern as the key and parser as the value. Allows the same parser to exist under different content type values. * Provide duplicate parsers for commonly seen content types * add tsv parser * add csv parser * Allow for arguments to be supplied to parsers * use other parsers to reduce copy/pasta
…o post_body_content_type
meztez
reviewed
Jul 3, 2020
This is masterfully crafted code. Beautiful. Loves the generalization where parser reuse other parser. Last time I've seen that great of a collab was Snoop & Dre. Seriously. Great stuff. |
|
schloerke
reviewed
Jul 3, 2020
schloerke
reviewed
Jul 3, 2020
schloerke
reviewed
Jul 7, 2020
schloerke
reviewed
Jul 7, 2020
meztez
reviewed
Jul 28, 2020
2 tasks
* master: Replace plus sign with space character when parsing a query string (#618)
Co-authored-by: Bruno Tremblay <bruno.tremblay@lacapitale.com>
cpsievert
reviewed
Jul 29, 2020
cpsievert
reviewed
Jul 29, 2020
cpsievert
reviewed
Jul 29, 2020
cpsievert
reviewed
Jul 29, 2020
cpsievert
reviewed
Jul 29, 2020
Co-authored-by: Carson Sievert <cpsievert1@gmail.com>
Co-authored-by: Carson Sievert <cpsievert1@gmail.com>
…lumber into post_body_content_type
Pop a can of Dr Pepper, you did it!!!! |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #583
Fixes #586
Reference: https://community.rstudio.com/t/uploading-tsv-files-to-plumber-api/71705/3
Changes:
application/octet
is provided, inspect the file name to see what it's mime-type is and use that as the content type value.application/octet
, but processed usingapplication/rds
which maps toparser_rds()
{
, but is truly plain text and not JSON.add_parser()
,parse_body()
, ...)PR task list:
devtools::document()
@meztez Can you take a look at this PR.