Problem/Motivation
While working on #2912363: LocalTaskDefault/LocalActionDefault ignore parameters when raw parameters are not present. it became clear that there is a great deal of shared concepts and code between the local actions and local tasks.
Bug fixes for one are needed for the other, which could lead to strange bugs if only one class is changed.
Proposed resolution
Define an interface for the shared portions of code, and provide a trait.
Remaining tasks
N/A
User interface changes
N/A
API changes
API addition:
LocalLinkInterface and LocalLinkTrait are now used by LocalActionDefault and LocalTaskDefault
Data model changes
N/A
| Comment | File | Size | Author |
|---|
Issue fork drupal-2995138
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
tim.plunkettThis incorporates the change from #2912363: LocalTaskDefault/LocalActionDefault ignore parameters when raw parameters are not present., so should be postponed on that once we're happy here.
Comment #4
tim.plunkettFixed the routeProvider mismatch
Comment #5
tim.plunkettComment #8
tim.plunkettReroll
Comment #17
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #19
andypostComment #22
quietone commentedConverted to an MR
Comment #23
smustgrave commentedShould we take this opportunity to add typehints and return types?
Comment #24
smustgrave commentedreturned to this one.
Technically I can see the argument to not include typehints but also see that we are touching this code to be moved to a brand new interface seems like a good time. Hence moving to NW
If you are another contributor eager to jump in, please allow the previous poster at least 48 hours to respond to feedback first, so they have the opportunity to finish what they started!