We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The plumber docs (as far as I can tell) do not show how to mark a parameter as required (or optional) without using the programmatic usage.
I would prefer to use the comment annotation as it is far easier to write and read.
Marking a parameter as optional is alluded to in the examples at https://www.rplumber.io/articles/annotations.html#equivalent-programmatic-usage-1. This is only shown for the programatic usage, however.
The text was updated successfully, but these errors were encountered:
I suppose for clarity,
I have a multipart endpoint like so:
This expects parameters:
How can I add documentation for this accordingly?
#* @post /upload upload <- function(req, res) { # parse the request multipart <- mime::parse_multipart(req) # ... }
Sorry, something went wrong.
No branches or pull requests
The plumber docs (as far as I can tell) do not show how to mark a parameter as required (or optional) without using the programmatic usage.
I would prefer to use the comment annotation as it is far easier to write and read.
Marking a parameter as optional is alluded to in the examples at https://www.rplumber.io/articles/annotations.html#equivalent-programmatic-usage-1. This is only shown for the programatic usage, however.
The text was updated successfully, but these errors were encountered: