Component Statement #575
Draft
Component Statement #575
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
Deprecate `pathAbsolute`
|
@TwitchBronBron we landed on Component Statement. Feel free to update the description. |
chrisdp
added
enhancement
…brighterscript into in-code-component
…ghterscript into in-code-component
…brighterscript into in-code-component
…ghterscript into in-code-component
…ctly parented (#973) Co-authored-by: Bronley Plumb <bronley@gmail.com>
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.
Adds an in-code way to define SceneGraph components without needing to mess with xml files.
TODO: add lengthier description as this feature progresses.
Is there a better name? I'm currently calling it
in-code component. NodeClass is alright but I really like using the word "component" in the name because that's what they transpile to.