Repository navigation
CSTM-566: Updating UI Plugins template to pull and merge skills when initing a new plugin - #262
Merged
Merged
Conversation
This file contains hidden or 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
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.
Description
UI Plugins will have both framework specific skills as well as general skills. To not repeat the skills in different directories in the ui-plugin-templates repo, the CLI needs to be able to pull skills from both the selected framework (currently just angular) as well as any repo-wide skills that apply to plugins regardless of frameworks and merge them into the generated plugin workspace.
See also PR: sailpoint-oss/ui-plugin-templates#15
How Has This Been Tested?
MV at CSTM-569