Performance: Use node directly in getValidations instead of searching by id #2688
+45
−54
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.
Description
splitDashedKey
showed up during profiling, this is used when searching for nodes usingfindById
. The case where this caused a problem was when getting validations for nodes, but in this case we can just use nodes directly instead of using nodeData and searching around. I also added a slightly slimmer funciton forfindById
that only returns the baseComponentId, but I am not sure it makes that much of a difference.Related Issue(s)
Verification/QA
kind/*
label to this PR for proper release notes grouping