Currently, there is no way to customize the behavior of App when an incoming request does not match with any listeners in the app. To improve this, we can extract these lines of code as a default behavior and enable developers to override the function in some way.
As we already have methods like oauth*Error, I'm thinking to name the new method as unhandledRequestError or something like that I went with unmatchedRequestHandler in AppConfig
Unlike other Bolt frameworks (JS / Python), Bolt for Java relays runtime exceptions to the external layer like Bolt adapters and its runtime. If a developer would like to handle the unmatched patterns in a single error handler, the recommended way is to throw an exception in the unhandledRequestError (the name is work in progress) method. I went with unmatchedRequestHandler in AppConfig
See also:
Category (place an x in each of the [ ])
Currently, there is no way to customize the behavior of
Appwhen an incoming request does not match with any listeners in the app. To improve this, we can extract these lines of code as a default behavior and enable developers to override the function in some way.As we already have methods like
oauth*Error, I'm thinking to namethe new method asI went withunhandledRequestErroror something like thatunmatchedRequestHandlerinAppConfigUnlike other Bolt frameworks (JS / Python), Bolt for Java relays runtime exceptions to the external layer like Bolt adapters and its runtime. If a developer would like to handle the unmatched patterns in a single error handler,
the recommended way is to throw an exception in the. I went withunhandledRequestError(the name is work in progress) methodunmatchedRequestHandlerinAppConfigSee also:
Category (place an
xin each of the[ ])