Skip to content
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

Properly sort marker resolution by relevance #2752

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

laeubi
Copy link
Contributor

@laeubi laeubi commented Jan 23, 2025

Currently the marker resolution is sorted, but markers with the lowest relevance are show on top, and therefore these are selected by default. This is confusing and gives a bad user experience, also this is the reverse order than we use when offering the quickfix in the editor itself.

This now sorts the list that the marker with the highest relevance is on top and selected by default.

Currently the marker resolution is sorted, but markers with the *lowest*
relevance are show on top, and therefore these are selected by default.
This is confusing and gives a bad user experience, also this is the
reverse order than we use when offering the quickfix in the editor
itself.

This now sorts the list that the marker with the highest relevance is on
top and selected by default.
Copy link
Contributor

Test Results

 1 818 files  ±0   1 818 suites  ±0   1h 31m 2s ⏱️ - 3m 33s
 7 715 tests ±0   7 487 ✅ ±0  228 💤 ±0  0 ❌ ±0 
24 306 runs  ±0  23 557 ✅ ±0  749 💤 ±0  0 ❌ ±0 

Results for commit 77c947c. ± Comparison against base commit 6d3c665.

@jukzi
Copy link
Contributor

jukzi commented Jan 23, 2025

OK, regression from f13fb49
however adding so many lines just to force your favorite style is questionable

@jukzi jukzi added bug Something isn't working regression labels Jan 23, 2025
@laeubi laeubi merged commit 935b1db into eclipse-platform:master Jan 23, 2025
17 checks passed
@laeubi
Copy link
Contributor Author

laeubi commented Jan 23, 2025

The "new style" was hardly readable, understandable and debugable and introduced bugs ... So yes I always prefer "more lines" if it makes the code more clear because code is written once and read often.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working regression
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants