We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is a good practice that package should correspond to the file path (or the other way around). Metals could show a warning when it doesn't.
Ideally, this warning should be easy to turn off because it might be annoying if one's working in the workspace when package and paths don't match.
none
No response
package warning diagnostics
The text was updated successfully, but these errors were encountered:
It would be really nice to include that as a Scalafix linting rule 🤔
Should be fairly simple to do that and can be configured by users themselves in the config file. Otherwise we risk the settings growing too much
Sorry, something went wrong.
Embedded in Metals or a standalone one?
It would be really nice to include that as a Scalafix linting rule thinking Embedded in Metals or a standalone one?
It would be really nice to include that as a Scalafix linting rule thinking
I would say embedded in Metals since it would otherwise need a BSP integration for each server.
No branches or pull requests
Is your feature request related to a problem? Please describe.
It is a good practice that package should correspond to the file path (or the other way around). Metals could show a warning when it doesn't.
Ideally, this warning should be easy to turn off because it might be annoying if one's working in the workspace when package and paths don't match.
Describe the solution you'd like
Describe alternatives you've considered
none
Additional context
No response
Search terms
package warning diagnostics
The text was updated successfully, but these errors were encountered: