[REF] Decouple crmD3 angular module from CiviMail #19047
Merged
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
Makes the D3 graphing library load in a more standard way.
Before
The
crmD3
module was being conditionally declared based on whether CiviMail is enabled, then automatically loaded on thecivicrm/a
base page.After
crmD3
module always exists, but is not automatically loaded on any base page. ThecrmMailingAB
will load it as a dependency.Technical Details
From the user's POV there is no change here. It just manages the Angular dependencies in a more standard, reusable way.
Comments
This is with an eye toward using D3 for Search Kit displays.