More path selectors for type, value and property value#137
Merged
Conversation
e081bf6 to
8e1647b
Compare
Rather than using a string to represent the component, we now use a class that can handle both name and property selectors. This allows us to add more complex selectors in the future without having to change the ItemPath class. It also moves the logic of parsing the component string from the scene to the ItemPathComponent class.
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.
This PR is heavily inspired by #107 and adds additional path selectors in the new framework introduced in #136
These selectors include:
They allow you to reference an object in a path through its attributes, without the need for assigning an object name.
The new selectors are documented in docs/item-path.md