Rubberduck: Using 'Fix all occurrences in project' on an aggregate inspection result only fixes one instance.

Created on 14 Feb 2017  路  4Comments  路  Source: rubberduck-vba/Rubberduck

Results when starting:
globalinspectionresulthasnoname2

Results after hitting 'Fix all occurrences in project' and waiting a few minutes for the inspections to rerun:
aggregatefixallonlyoneinstanceafter

bug critical feature-inspections
Source
picture MDoerner

Most helpful comment

This was fixed a few PR's ago, back when I rewired the quick fixes after rewriting them.

picture Hosch250 on 10 May 2017
👍2

All 4 comments

It seems that this also applies for "Fix all occurrences in module". It only fixes the first occurrence.

mbl123 picture mbl123 on 6 Apr 2017

This is somewhat nontrivial for both cases, since the AggregateInspection doesn't really know which inspection it aggregates.

Additionally this is blocked by the refactoring around Inspections in the works at #2951

Vogel612 picture Vogel612 on 9 Apr 2017

@Hosch250 I need to check, but did your last PR fix this?

retailcoder picture retailcoder on 10 May 2017

This was fixed a few PR's ago, back when I rewired the quick fixes after rewriting them.

Hosch250 picture Hosch250 on 10 May 2017
👍2
Was this page helpful?
0 / 5 - 0 ratings

Related issues

SteGriff picture SteGriff  路  3Comments
retailcoder picture retailcoder  路  3Comments
ThunderFrame picture ThunderFrame  路  3Comments
susnick picture susnick  路  3Comments
ghost picture ghost  路  3Comments