Skip to content

resolve getter/setter references with different scopes before combining docs #2693

Open
@jcollins-g

Description

@jcollins-g

The new lookup code is going to skip over this problem much as the old one does, but it is still an issue. WRT comment reference resolution, each accessor in a GetterSetterCombo potentially has a different resolution grandparent (definingLibrary). This means that comment references in each piece of a Field or TopLevelVariable should be resolved with that context in mind. Currently the docs just get squished together meaning one accessor or the other could resolve with the wrong scope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2A bug or feature request we're likely to work ontype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)type-code-healthInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainable

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions