Refactor how the ATH::Action for a given request is resolved
#653
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.
Context
Follow up to #636 that makes use of #652 to store the
_actiondirectly within the route defaults. This removes the needs for an extra mapping layer from controller name toATH::Action. I kept_controlleras a means to more easily tell what controller action handled the request.Changelog
ATH::Actionfor a given request is resolvedATH::ActionResolverand interfaceBefore merging, remember to add the
athena-framework/athenaprefix to the PR number in the PR title