perf: add .skip(1) to .ancestors() calls in a bunch of places#9330
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (29)
WalkthroughThis PR systematically adds Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
Merging this PR will not alter performance
Comparing Footnotes
|
Merging this PR will not alter performance
Comparing Footnotes
|
Summary
There were a bunch of places where we were calling
.ancestors()and not skipping the first in the iterator, which is the current node and not a parent.I think ideally we would provide a separate iterator that doesn't have the current node in the first place.
No changesets because the perf improvement probably won't impact most people.
Test Plan
snapshots
Docs