Skip to content

Following library module references in import statements in an editor leads to spurious errors on non-existing RASCAL.MF files #986

@jurgenvinju

Description

@jurgenvinju

Describe the bug

Image

I followed the reference to three library modules in three different editors for the same project, and these errors appeared in the diagnostics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions