[INTERNAL] Extension handling groundwork #46
Merged
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
See [RFC0001](SAP/ui5-tooling#4). Identify and apply extensions in dependency tree so that they can influence the actual project processing.
Also enhance extension metadata checks
Used in npm scripts. Already a dependency in all other tooling modules
And fix shimed dependency and collection handling
Pull Request Test Coverage Report for Build 198
💛 - Coveralls |
|
@matz3 ping |
matz3
approved these changes
Oct 16, 2018
RandomByte
changed the title
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.
Identify and apply extensions in dependency tree so that they can influence the processing of a project.
Implements foundation for "extensions" as required in RFC 0001 (Type Extensibility) and RFC 0004 (Simple Build Extensibility)
Implements shim extensions as defined in RFC 0002 (Project Shims)