One of the quick fixes suggested for this warning is "Try to generify" the file. If I choose and apply it, nothing changes in the file (it cannot be generified more than it has been done) with no visual indication that nothing has been done (perhaps a separate issue). The warning "Unchecked assignment" survives. However, now the quick fix "Try to generify" is no longer suggested. It is started being suggested again once I change something in the code of the file. Apparently the fact this quick fix has been suggested is cached somewhere and the cache gets invalidated on any change. My claim is that the behavior is difficult to understand for an ordinary user.
Suggestions:
1) Provide a visual feedback (e.g. a tooltip) if the "Try to generify" doesn't do anything to code.
2) Make "Try to generify" being suggested regardless of the past - this fact IMO shouldn't be cached
One of the quick fixes suggested for this warning is "Try to generify" the file. If I choose and apply it, nothing changes in the file (it cannot be generified more than it has been done) with no visual indication that nothing has been done (perhaps a separate issue). The warning "Unchecked assignment" survives. However, now the quick fix "Try to generify" is no longer suggested. It is started being suggested again once I change something in the code of the file. Apparently the fact this quick fix has been suggested is cached somewhere and the cache gets invalidated on any change. My claim is that the behavior is difficult to understand for an ordinary user.
Suggestions:
1) Provide a visual feedback (e.g. a tooltip) if the "Try to generify" doesn't do anything to code.
2) Make "Try to generify" being suggested regardless of the past - this fact IMO shouldn't be cached