Skip to content

Code Inspection for VB_Description doesn't stay in sync with description #4947

@IvenBach

Description

@IvenBach

Version 2.4.1.4627
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office 2013 x86
Host Version: 15.0.5111.1000
Host Executable: EXCEL.EXE

Description
First description given to a module will remain even after description is updated via Object Browser.

To Reproduce
Steps to reproduce the behavior:

  1. Add a module. Object Browser>Select Module>RightClick Context Menu>Properties and giving a description: Foo
  2. Edit module in any way. Not editing module doesn't cause inspection to come up. ¿Possible bug itself?
  3. Parse with RD.
  4. Display Code Inspections. Member 'Module1' has a 'VB_Description' attribute with value(s) "'Foo'". but no corresponding annotation.
  5. Edit via object browser to another description: Duk. Reparse
  6. Review Code Inspection and see old description remain.

Expected behavior
Each reparse should have the current description.

Additional context
Came across this issue from testing in chat. Was able to have both a '@ModuleDescription Foo and description added without having this inspection come up. Naturally I can't repro the initial non-inspection result.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIdentifies work items for known bugs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions