More explanations on match patterns in router forwarding #235
Conversation
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
Updates for record->structs for 0.13.2
Deps version rev and deprecation updates
|
I just find out that if we use :compile_on_demand option, i.e, default at dev environment, route file name MUST BE underscore name of the router module, otherwise our router module is not gonna be compiled, and an exception of "FunctionNotDefined for service/1" will eventually be raised. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
My first impression was that router forwarding works for simple cases like in the example, but no,
forwardtakes exactly whatget/posttakes, so I tried to make it clearer.