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
When defining plumber routers with comments, function parameters are inferred and matching query string parameters are automatically passed to the underlying function. Similar behavior is expected when programmatically defining handlers using the $handle method. However, the following error results:
library(plumber)
pr<-plumber$new()
pr$handle("GET", "/add", function(x, y) sum(as.numeric(x), as.numeric(y)))
pr$run()
#> Error in endpointParams[[p]] : subscript out of bounds
Full error traceback:
6. priorizeProperty(defaultApiType, endpointParams[[p]]$type, funcParams[[p]]$type) at openapi-spec.R#98
5. parametersSpecification(routerEndpointEntry$params, pathParams,
funcParams) at openapi-spec.R#19
4. endpointSpecification(endpointEntry, join_paths(parentPath, endpointEntry$path)) at plumber.R#1119
3. private$routerSpecificationInternal(self) at plumber.R#916
2. self$apiSpec() at plumber.R#319
1. pr$run()
The text was updated successfully, but these errors were encountered:
When defining plumber routers with comments, function parameters are inferred and matching query string parameters are automatically passed to the underlying function. Similar behavior is expected when programmatically defining handlers using the
$handle
method. However, the following error results:Full error traceback:
The text was updated successfully, but these errors were encountered: