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.
Overview
This adds the shell of the event cart extension - at this stage it's purely civix generated and is a component portion of
#17508
There is a long-standing technical desire to separate core out into a more modular and less interdependent structure. This includes such things are using the same methods available to extensions for parts of core to interact with each other and potentially, eventually, allowing portions of it to be disabled by some sites or even moved out of the core repo to be managed by other maintainers at a different development pace (in some cases this would be part of a obsolescence strategy - e.g the core implementation of PaymentExpress (NZ payment provider) is superceded in the Omnipay extension so the eventual goal of a strategy to extensionize that processor would be for it to no longer be in core or maintained
Before
No steps yet merged towards the goal of separating out event cart
After
A shell extension is not in the ext directory - the various code needs to be moved into this extension and we need routines to enable it. However, the challenges of improving civix to the point where a new extension would pass code style were not trivial and we are treating that as step one.
Technical Details
Generated with the command civix generate:module eventcart --author="CiviCRM" --email="info@civicrm.org"
Comments
Adding the generated code first makes later changes very transparent / reviewable