We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
findPath
Improvement.
Right now findNode is used, and then since it's easiest we end up using node.key for subsequent lookups.
findNode
node.key
If there was a findPath DOM helper instead, all of the subsequent lookups could use paths also instead of keys.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Do you want to request a feature or report a bug?
Improvement.
What's the current behavior?
Right now
findNode
is used, and then since it's easiest we end up usingnode.key
for subsequent lookups.What's the expected behavior?
If there was a
findPath
DOM helper instead, all of the subsequent lookups could use paths also instead of keys.The text was updated successfully, but these errors were encountered: