Skip to content

limiting of lint errors and auto-fix #6

@JohnRDOrazio

Description

@JohnRDOrazio

I found in my initial tests, that if we let the linter mark ALL of the linting issues in the source editor, then the UI would freeze for quite a while. I couldn't find a good way to background this kind of job, so I wound up just limiting the number of linting issues that are marked in the source editor. However this does create an inconsistency: while the linting issues at the bottom of the source editor do correspond to the ones that are marked in the source (they are both constrained to the same limit), however all of the linting issues are shown in the class view. If you navigate from the class view to the source, you won't always see the issue, because it might not fall within the limited set that are shown in the source.

We need to think of a good way to handle this (perhaps mark the issues in source if not already marked when navigating from class view to source view?)

In any case one of the next things to tackle would be an auto-fix for the linting issues, perhaps with AI assistance (I'm not sure there are currently any linters for OWL or Turtle that have auto-fix features?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions