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
─ Session info ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
setting value
version R version 4.2.1 (2022-06-23 ucrt)
os Windows 10 x64 (build 19044)
system x86_64, mingw32
ui RStudio
language (EN)
collate English_United States.utf8
ctype English_United States.utf8
tz America/Chicago
date 2022-09-09
rstudio 2022.02.0+443 Prairie Trillium (desktop)
pandoc NA
! package * version date (UTC) lib source
plumber * 1.1.0 2021-03-24 [?] CRAN (R 4.2.0)
Example application or steps to reproduce the problem
#* @get /columnsgetColumns=function(req) {
stop("I'm an error in dataController!")
# ...
}
Describe the problem in detail
Trying to setup a global error handler and it appears to not be working for any endpoints defined in a mounted file. Running the above plumber code will result in "/simple" and "/trouble" returning the custom error message but "/data/columns" does not. Is there something special I need to be doing for mounted files to be included with the custom error handler?
The text was updated successfully, but these errors were encountered:
schloerke
changed the title
pr_set_error() doesn't work for mounted files
Should mounted routers inherit error/404/serializer/etc from parent mount if non have been set?
Sep 29, 2022
System details
Example application or steps to reproduce the problem
plumber.R:
./controllers/data.R:
Describe the problem in detail
Trying to setup a global error handler and it appears to not be working for any endpoints defined in a mounted file. Running the above plumber code will result in "/simple" and "/trouble" returning the custom error message but "/data/columns" does not. Is there something special I need to be doing for mounted files to be included with the custom error handler?
The text was updated successfully, but these errors were encountered: