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

Scala CLI should be able to report actionable diagnostics #558

Closed
romanowski opened this issue Jan 19, 2022 · 1 comment
Closed

Scala CLI should be able to report actionable diagnostics #558

romanowski opened this issue Jan 19, 2022 · 1 comment
Assignees
Labels
Linting A group of issues related to anaylze configuraion provided to Scala CLI UX

Comments

@romanowski
Copy link
Member

Scala CLI can report warnings / errors over CLI and BSP (so it is displayed in Metals). The idea is that some of those diagnostics to contain actionable part to fix the problem. For example, warnings about the deprecated syntax of using directives can provide a way to just change the syntax with one command or one click.

The IDE/BSP part would most likely needs changes in BSP protocol so this issue should over only command line part. Based on the results of this task we should plan and discuss a solution that will work also with Metals.

@romanowski romanowski added Linting A group of issues related to anaylze configuraion provided to Scala CLI UX labels Jan 19, 2022
@lwronski
Copy link
Contributor

lwronski commented Nov 23, 2022

The mechanism was implemented in scala-cli and Metals. If users want to enable actionable diagnostics, they must run scala-cli config actions true. A actionable diagnostic is generated that provides suggestions that can be applied to your code, as has already been done in Metals.

Screen.Recording.2022-11-05.at.11.14.15.mov

Future work is tracked here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Linting A group of issues related to anaylze configuraion provided to Scala CLI UX
Projects
Archived in project
Development

No branches or pull requests

2 participants