Inspection: Typo in comment is not thrown into the problems

Hi. I have the Rider 2023 version.3.3 Build RD-233.14015.60 / dated January 18, 2024

If I change configure inspection severity to Error / Warning for Inspection: Typo in comment, I expect to get all the places with this error in Problems. But this is not happening.

If this is a bug, please fix it. If not, tell me how to set up / where to view errors in the comments on the project.

update 09.02:

Inspection: 'Redundant empty argument list on object creation expression' - is displayed as a Warning about Problems, but it is not for this reason that it is highlighted in yellow in the code.
Only when you change the Severity setting of the Error check, the light will turn red.
This Is it a bug or is that what it's meant to be? Is it possible to change this somehow?


-----------------------------------------------------

Привет. У меня версия Rider 2023.3.3 Build RD-233.14015.60 / от 18 января 2024

Если я меняю configure inspection severity на Error / Warning для Inspection: Typo in comment, я ожидаю получить в Problems все места с данной ошибкой. Но этого не происходит.

Если это баг - прошу зафиксировать. Если нет - подскажите - как настроить / где посмотреть ошибки в комментариях по проекту.

update 09.02:

Inspection: 'Redundant empty argument list on object creation expression' - отображается как Warning в Problems, но почему то не подсвечивается в коде желтым цветом.
Только когда изменяешь его Configure inspection severity на Error - начинает гореть красным.
Это баг или так и задумано? Можно ли это как то поменять?

0
9 comments

Hello,

Are you referring to regular comments, multiline comments, or XML doc comments? Is the typo highlighted in the editor? A screenshot would be very helpful as well.

Thank you in advance.

0

Here is an example on the first question:

I expect to see Typo in comment errors in the entire solution, not just in the current file tab.

----

Вот пример по первому вопросу:

Я ожидаю увидеть ошибки Typo in comment во всем солюшене, а не только во вкладке текущего файла.

 

0

2 question regarding the yellow undertone:

-----

2 вопрос, касательно желтой подцветки:

 

0

Hello,

Thank you for the clarification. 

I expect to see Typo in comment errors in the entire solution, not just in the current file tab.

The All Solution Files view is populated by the Solution-Wide Analysis feature. This feature does not use the Typo in comment inspection (you can check the list of inspections it uses), thus these results are not present in this tab. If you need to run this inspection against the entire solution, you can use the Run Inspection By Name feature. This action can also be invoked using the context actions menu:


 

Inspection: 'Redundant empty argument list on object creation expression' - is displayed as a Warning about Problems, but it is not for this reason that it is highlighted in yellow in the code.

Thank you for reporting this issue. I have been able to reproduce it and filed a bug report to our tracker: RIDER-106028 "Redundant empty argument list on object creation expression" not highlighted in the editor. Please upvote the request to indicate your interest and follow it for status updates.

0

Everything is clear. Thanks for the help. I will monitor the progress of the Bug.

---

Все понятно. Спасибо за помощь. Буду следить за ходом Бага.

0

The same mistake (no yellow undertone), but for a different reason

---

Та жа ошибка (нет подцветки желтым), но по другой причине

0

Regarding the last two screenshots, could you please clarify where do you expect the highlighting and what the highlighting is it supposed to be?

0

In C#, right now, you don't have to put parentheses after the `namespace`. They are grey. They should be highlighted.

----

В C#, сейчас, после `namespace ` можно не ставить скобки. Они серые. Они и должны подсветиться. 

0

Hello,

We have reviewed the logic behind this highlighting and, as stated in the comment in RIDER-106028, it currently works as designed, both in case of redundant parentheses in new Foo(); and in case of curly braces in a block-scoped namespace declaration. These characters are highlighted in dark grey to indicate redundancy, no yellow underline highlighting is expected. Please accept my apologies for the confusion with this. 

0

Please sign in to leave a comment.