Fixing how Stereotypes and Profiles are identified and consumed by Player Piano #23
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
…icated branch on different fork
Updates documentation to match the new profile identification method used in patterns
|
This now completely addresses issue #21 with updated documentation of the pattern format |
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.
Updates Player Piano to identify profiles for stereotypes based on profile name or qualified name.
Updates all provided pattern files to use a consistent format for stereotype and profile information that is compatible with the Player Piano fix.
This addresses Issues #8, #9, and #17.
Most of Issue #21 is addressed by this fix except for any desired changes to the patterns README (or elsewhere) to document how patterns should be formatted
Note that this fix is unrelated to the root cause of Issue #22 but is definitely required before #22 can actually be solved