Feature-Request: Third option to cycle through issues
Hi,
as you know, i can cycle through the issues in a file by pressing “F2” or by using the buttons in the top-right corner of the editor.
It is even possible to configure the order:
I would like to suggest a third option:
“Errors first, then all remaining Problems”
Reason:
The “finished” state of a file is:
- All errors are resolved
- Some warnings and suggestions might remain.
As long as a file contains any errors, I need “Problems with Highest Priority”, since I need to fix all the errors.
Once the errors are gone, I need “All Problems” in order to cycle through all remaining problems and decide whether they should remain in the code or not.
Thus I do regularly switch between the settings (which are not really nicely accessible). This could be avoided if there was the option “Errors first, then all remaining Problems”.
Please sign in to leave a comment.
As the Classic UI is deprecated, in the New UI you can sort the problems by severity. There is no plan to update the Classic UI in the future.
A question for this feature: with all highest priority problems being resolved, when pressing F2, it will iterate through the remaining problems by default.
This design can ensure the user always focuses on the highest priority problems.
For your situation, if all errors get resolved, pressing F2 will start iterating the remaining warnings – as they are the highest priority now. Does it match your needs?
“For your situation, if all errors get resolved, pressing F2 will start iterating the remaining warnings – as they are the highest priority now. Does it match your needs?”
No, because warnings may remain in the code.
Fixing the errors is mandatory for each developer. Thus cycling through the errors first is the best choice.
But after fixing the errors, there is no comfortable way to cycle through all remaining issues.
Please refer to the GIF.
By default, when all errors get resolved, pressing F2 will iterate through all the warnings.
And what about typos?
If there is only a single warning that should remain, your process will never reach typos.
In order to reach these, you need to change the cycle-priority then, which is not very comfortable.
And that's why I posted this feature-request.
If all “error” or “warning” level problems are resolved, press F2 will go through the rest of “hint” levels.
I'm a bit confused about your description, if you select Go through “All Problems” with F2, and reorder the list of problems, you will be able to cycle through “Error” → “Warning” → “Hint” levels; If you just keep using “Go through the problems with the highest priority”, it will cycle through all “Error” levels, then “Warning” and “Hint” levels.
You are correct, that this is possible. But it makes me switch these options regularly.
Just imagine a normal workflow while coding:
I open a file with some errors, warnings and typos.
As long as there are errors, I need the setting “Go through the problems with the highest priority”. Because all errors need to be fixed before the warnings become interesting. And I have to fix the errors anyway before the code will work.
But as soon as the errors are fixed, this setting does not work for me anymore.
Because often, a codefile contains a single warning that is there to stay and a dozen typos I would like to fix. I can hit F2 as often as I want in such a file. Rider will just stick to the warning.
Thus, I need to change this option to “All problems"
This works fine then. I do then fix the issues I deem necessary to be fixed and move on to the next file.
Then, there are errors again and I need to change this option again to “Go through the problems with the highest priority” in order to concentrate on errors. And after fixing the errors, I do switch back.
While this process is possible, it is not very convenient to change this setting back and forth all the time.
That is why I suggested the setting above:
“Errors first, then all remaining issues”
For me, and probably many other developers as well, this would reduce the amount of changes necessary to zero.
For your scenario, how about just using the Up/Down keys to iterate through all the problems in the Problem Tool window? Use “Ctrl + Tab” for quick navigation to the Problem Tool window, then navigate to the inspections you are interested in. I suddenly realized this matter when drafting a feature request.
Warnings and Hints are not in the equal priority. Some errors will not block application compiling and running, especially for the errors provided by code inspection rules. You can customize inspection severity levels in the IDE.
You could also submit the feature request with more scenarios on YouTrack.