Conversation
|
can I get "params" or "params.query" in custom service methods? |
Member
Author
|
@elixiao Yes, you always do in any service if you call it through REST or websockets. You will have to pass |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request adds a
service._setup(app, path)method that allows registering conflicting routes as reported in and closes #86. Works as described in the documentation added:setupwill be called after all REST routes have been set up. This means that youcan't register custom middleware with potentially conflicting paths.
In this case, implement
_setup(app, path)instead which will run before the RESTmiddleware is registered. An example would be implementing a
todos/countroutewhich returns the number of todos (instead of the todo with the id count):