[4.0] Namespace com_privacy #24586
Merged
[4.0] Namespace com_privacy #24586
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 29 commits
April 14, 2019 11:44
…paced and the factory tries to build stuff for the current component
added 10 commits
April 14, 2019 11:44
|
Thankyou!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of Changes
Namespaces and migrates com_privacy to 4.0 structure. Adds class map aliases for component classes used in plugins which helps deal with the issue of resolving plugin parameters by not requiring
JLoader::register()statements in every plugin and provides a compatibility layer between 3.x and 4.0.Note only PHP code is changed, the design team can do template stuff.
Testing Instructions
The component works.