-
Notifications
You must be signed in to change notification settings - Fork 30.6k
New issue
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
Implement new find functionality in Explorer view #232964
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tests would also be nice 😄
try { | ||
node = this.getDataNode(element); | ||
} catch { | ||
console.log('Error in _updateChildren'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bad idea. If this happens, the tree will be in a very bad state and there's no recovering from here. So we want the error to be thrown instead of quietly logging and pretending everything is fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this indeed is something that is happening, we must dig into the root cause and fix the issue upstream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching this, I added it for debugging reasons but forgot to remove it.
Introduce methods for marking and unmarking items as find results, along with a mechanism to prevent refreshing the view when phantom elements are present. Additionally, add a context key to indicate when the find provider is active.
fixes #233185