Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

false positive warning about library files not being well-supported #479

Closed
jurgenvinju opened this issue Oct 16, 2024 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@jurgenvinju
Copy link
Member

image
@jurgenvinju jurgenvinju added the bug Something isn't working label Oct 16, 2024
@jurgenvinju
Copy link
Member Author

This happens for all standard library modules, and also for well-configured dependencies in other libraries.

@PaulKlint
Copy link
Member

I have also seen this and had no idea what it meant, whether this was harmful or what to do about it.

Question 1: who generates this and why?

@jurgenvinju
Copy link
Member Author

If you open a file outside of the srcs folders in the pathconfig then editor features like the static checker don't work well. The rascal lsp server checks this and produces the error.

I think it doesn't consider files in library folders that have .tpl files. Because these are also well supported by the LSP server.

@DavyLandman
Copy link
Member

We got to improve this heuristic to not fire for library files that are openend, as we have special support for them.

Also, we discussed that missing pom.xml files see #443 and #434 should be fined tuned a bit more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants