Composite global aliasing with boolean switch #301
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
|
|
|
@briangann tagging for visibility |
|
sorry for the delay, will review this shortly! looks like a great addition |
briangann
added
no stalebot
briangann
approved these changes
Sep 28, 2023
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.
This enhancment makes global aliasing truly global. Composite names now also receive global aliasing if global aliasing is toggled to
truein composites dropdown.Changes:
I have not had the ability to create new tests to ensure future reliability of this feature. This is one thing I could use some help on, if possible, since I am not great at creating react-style tests.
Please let me know if further adjustments are required. Thanks!