From e506f25a82e5d45ec8e0ed88438f5b96ea06d3cc Mon Sep 17 00:00:00 2001
From: Dmitry Jemerov
- This inspection will use the exclude settings from the plugin configuration to ignore classes having fields
- not supposed to be dumped.
-
- This inspection can use on-the-fly code inspection by enabling it to show errors as warnings. This will highlight
- the classname on-the-fly in the java editor.
-
- Notice 'on-the-fly' should be enabled from the settings to this plugin.
This inspection reports any classes with no toString() method.
-
An additional settings is to exclude certain classes by using a regular expression
- matching the classname.
-
Exception, deprecated, abstract or enum classes can also be excluded.
-
|
- This insepction is used to identify out of synchronization situations
- where you have an existing toString() method that dumps the fields. However some fields have been added to the class
- later and these new fields are not dumped in the toString() method.
+ This inspection reports any fields which are not used in the toString() method of the class. This can be useful to discover
+ fields that were added after the toString() method was created and for which the toString() method was not correctly adjusted.
+ It is possible to exclude fields from this check in the settings accessible via the Generate > toString() dialog.
This inspection will also check for problems with getter methods if 'enable getters in code generation' is enabled in settings. - - This inspection can use on-the-fly code inspection by enabling it to show errors as warnings. This will highlight - any unused fields on-the-fly in the java editor - also the right gutter will indicate the location of the error using - a yellow marker. This is the same feature as the build in inspection 'Field XXX is never assigned'. - - Notice 'on-the-fly' should be enabled from the settings to this plugin. |