-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Improving search results #5174
Comments
@TylerJewell does closing this issue mean it won't be considered in the epic or..? |
@davidwindell - I am just bulk closing a lot of older issues right now that are kind/enhancement and then allowing dev teams or other contributors to re-open them if they have a reasonable confidence it will be implemented in the upcoming 6 months or so. We have a large backlog of enhancement requests and trying to sort out which ones are more wishes that we cannot likely ever get to vs. those that are part of an upcoming dev plan. The backlog had 600 issues opened at start of the day and it's too big to properly manage, so trimming shears are out! |
@TylerJewell I got pinged on a couple of these. Thanks for the reasoning, I guess I just wanted to check that the "epics" you are leaving open that refer back to my feature requests/issues (you've now closed) will still be considered? Like this one for example. |
Yeah, the epics are all still valid and all intentions are that dev teams will be assigned to them over the coming year. |
We will work on it soon here https://github.com/eclipse/che/tree/searchwithpossitions |
That's awesome news! Ping @broopdias |
One of the main things we are missing coming from using a desktop IDE (Netbeans in my case) is a search feature that shows line numbers and links to the result in the file.
Please refer to the screenshot below:
The key features are;
Most of the work I do relies heavily on the ability to quickly find basic strings across a very large project and at the moment I can't work in Che on the project because of this limitation.
Thanks!
The text was updated successfully, but these errors were encountered: