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
{{ message }}
This repository has been archived by the owner on Jan 15, 2022. It is now read-only.
There is the halts option in Macaw that for default is false. That means that even if a match is found, Macaw continues trying to match the current uri with other routes.
That makes me wonder, what happens if another route matches and the controller@action for the first match was already executed and provides some output? The second controller@action is also executed and provides output?
Looking at the code seems that $halts should be always true for a correct behavior.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is the halts option in Macaw that for default is false. That means that even if a match is found, Macaw continues trying to match the current uri with other routes.
That makes me wonder, what happens if another route matches and the controller@action for the first match was already executed and provides some output? The second controller@action is also executed and provides output?
Looking at the code seems that $halts should be always true for a correct behavior.
The text was updated successfully, but these errors were encountered: