Add configuration setting for 'route action middleware' #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements #265
Specifically, a developer can define additional middleware for route actions.
This change allows my server to successfully add my Oauth2.0 scope checks to my desired API endpoints.
I can successfully set the scopes as
User.Group.Update
orUser.Chat.Update
to my tokens, and be blocked on API requests if I don't have the required scope.Note, that for my case, I defined a closure that I provide to each call of the
routeActionMiddleware
function. I'd still like to have it defined on the server once, but didn't see a way to implement that without significant refactors.Finally, I can definitely clean this up as desired. Let me know if a different name/key is preferred, or if you want me to remove the type annotations.