Mathieu Guindon
Mathieu Guindon
I'll be revisiting the website content soon-ish; I'd like to document under what circumstances the refactorings are enabled, because they are context-dependent. But most of Rubberduck is disabled until there's...
Definitely! I think I'm going to merge my incomplete stuff in... quite important refactorings and modifications to inspections have been waiting in my fork forever (I need a `TimeFactory`)...
I like this one, I think a basic implementation could be in-scope for v2.x, perhaps with some false negatives for the code path cases.
This feels very similar to the Excel-specific inspection around late-bound `Application` member calls.
This should be offered as a quickfix for the _Side-effecting IIf_ inspection, which already picks up the targets for this.
Isn't "at least one call" already covered by *procedure not used*?
`@MustExecute` annotation could be parameterized with some enum values - a usability prerequesite would be code pane subclassing and hijacking of IntelliSense so annotation parameters can have autocompletion.
For this to work we need visibility on project-level compiler constants.
Adding to v2.x since we do have all the constants now, but only the "live" path can be evaluated. Not sure if reporting on one path but not for any...