Greater prominence #13

New Issue

2023-12-10T10:33:34+01:00

Ghost commented

2023-12-10 10:33:34 +01:00

Your quip about getting zero feedback is possibly due to the hidden nature of this plugin. It took me a while to figure out that, unlike every other plugin I've used, this one is simply a collection of inspections.

Before installling the plugin I wrote tests with whatever default inspections were available. So after installing the plugin the first thing I want to do is run all the possible inspections over my entire project.

However, when I view all the AssertJ inspections in the settings I cant tell which are due to the Cajon plugin. I could be all, some or none. How would I know? I'm unlikely to keep the plugin if its unclear what value it provides.

Suggestion: add "Cajon: " prefix to the name of every inspection OR add a marker like how intellij lets you know about new inspections

Your quip about getting zero feedback is possibly due to the hidden nature of this plugin. It took me a while to figure out that, unlike every other plugin I've used, this one is simply a collection of inspections. Before installling the plugin I wrote tests with whatever default inspections were available. So after installing the plugin the first thing I want to do is run all the possible inspections over my entire project. However, when I view all the AssertJ inspections in the settings I cant tell which are due to the Cajon plugin. I could be all, some or none. How would I know? I'm unlikely to keep the plugin if its unclear what value it provides. Suggestion: add "Cajon: " prefix to the name of every inspection OR add a marker like how intellij lets you know about new inspections ![image](/attachments/542fdd61-b74f-422c-9869-c322ed416a90)

image.png

35 KiB

chrisly42 commented

2023-12-10 13:12:05 +01:00

Hi there,

indeed it is a collection of inspections with intentions. They are all listed in the AssertJ section as shown in the image below. Once you have activated the plugins intention (which should be the default unless you turned that off in your IDE prefs) and usually keep your code free of warnings, you should see them pop up in your editor immediately.

You can also use the "Run Inspection by name" action / menu item (e.g. to run an inspection over your whole code base), which will also list the source of the inspection. As you can see, most of the assertions start with "Assert". The IDE will also filter out other inspections if you use the name of the section the inspections are in, which in the case for Cajon would be "AssertJ".

It is not convenient to add a prefix to the name of the inspection, and as shown, this not even necessary.

Hi there, indeed it is a collection of inspections with intentions. They are all listed in the AssertJ section as shown in the image below. Once you have activated the plugins intention (which should be the default unless you turned that off in your IDE prefs) and usually keep your code free of warnings, you should see them pop up in your editor immediately. You can also use the "Run Inspection by name" action / menu item (e.g. to run an inspection over your whole code base), which will also list the source of the inspection. As you can see, most of the assertions start with "Assert". The IDE will also filter out other inspections if you use the name of the section the inspections are in, which in the case for Cajon would be "AssertJ". It is not convenient to add a prefix to the name of the inspection, and as shown, this not even necessary.

Screenshot 2023-12-10 at 12.57.09.png

307 KiB

Screenshot 2023-12-10 at 13.05.28.png

244 KiB