Skip to content

Rubberduck should use Rubberduck.Folder.Annotations rather than Project.Module when you select "group by location" #5846

@Greedquest

Description

@Greedquest

Rubberduck should use Path.To.Folder rather than Project.Module when you select "group by location". Otherwise, what's the point in all our nice '@Folder annotations:
image

Given the code inspections require a successful parse, the folder annotations should always be available when code inspections are.

I propose getting rid of the other option entirely, or adding a group by module option for the old behaviour and make group by location do the Rubberduck way.

The default alphabetical sorting is sufficient, an expansion would be to bring the collapsible folder tree into the code inspections window (indeed the whole of project explorer with search and filtering options could be interwoven into the code inspections window to make locating inspection results much more seamless).

Metadata

Metadata

Assignees

No one assigned

    Labels

    difficulty-02-duckyResolving these involves the internal API, but with relatively easy problems to solve.enhancementFeature requests, or enhancements to existing features. Ideas. Anything within the project's scope.up-for-grabsUse this label in conjunction with a difficulty level label, e.g. difficulty-02-duckyuser-interfaceThis issue explicitly relates to the visible interface of Rubberduck.wpfIssue is easier to resolve with knowledge of WPF/XAML

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions