Merge branch 'main' into zip_attachment_example

DESCRIPTION

@@ -54,7 +54,7 @@ Suggests:
     redoc,
     rapidoc,
     sf
-RoxygenNote: 7.2.2
+RoxygenNote: 7.2.3
 Collate:
     'async.R'
     'content-types.R'

vignettes/routing-and-input.Rmd

@@ -310,7 +310,21 @@ Alternatively, `echo {"id":123, "name": "Jennifer"} > call.json & curl --data @c
 
 As demonstrated above, the raw request body is made available as `req$bodyRaw` and parsed request body is available as `req$body`.
 
-If multiple parameters are matched to the endpoint formals, an error will be thrown. Due to the nature of how multiple values can be matched to the same argument, it is recommended that `POST` endpoints have a function definition that only accepts the formals `req`, `res`, and `...`. If the endpoint arguments are to be processed like a list, they are available at `req$argsBody`, with all arguments at `req$args`. `req$args` is a combination of `list(req = req, res = res)`, `req$argsPath`, `req$argsBody`, and `req$argsQuery`.
+#### Named parameters collision note
+
+Only the first matched formal arguments are passed automatically to the endpoint during execution. Duplicates are dropped. Query parameters have priority over path parameters, then finally, body parameters are matched last.  
+
+While not required, it is recommended that endpoints have a function definition that only accepts the formals `req`, `res`, and `...` to avoid duplicates. If the endpoint arguments are to be processed like a list, they are available at `req$argsBody`, with all arguments at `req$args`. `req$args` is a combination of `list(req = req, res = res)`, `req$argsPath`, `req$argsBody`, and `req$argsQuery`.
+
+``` r
+function(req[, res, ...]) {
+  ...
+  req$argsQuery
+  req$argsPath
+  req$argsBody
+  ...
+}
+```
 
 ### Cookies {#read-cookies}
 

vignettes/tips-and-tricks.Rmd

@@ -109,8 +109,6 @@ function(req, res){
 If you run this API locally and then visit the API in a web browser, you'll see your R session switch into debug mode when the request arrives, allowing you to look at the objects contained inside your `req` and `res` objects.
 
 
-### Plumber Server
-
 ## Port Range
 
 You can use [httpuv::randomPort()] to define a range of port for Plumber to pick from when running an API.