Skip to content

Better clues on how to fix and more robust semanticdb #453

@oharboe

Description

@oharboe

Is your feature request related to a problem? Please describe.

We have a procedure to make semanticdb work.

  1. bazelisk build ... (includes all targets in .bazelproject)
  2. Open file you are interested in that is missing semanticdb in Metal Doctor. Make a change that is more than just a whitespace change, such as val fix = 42
  3. Let it rebuild, now I get semanticdb. Undo the change in 2. Code is white instead of colored.
  4. Close vscode and reopen
  5. Finally, everything works and all code is now colored. 😌

Describe the solution you'd like

It should just work or Metals Doctor should tell me exactly what I should do

Describe alternatives you've considered

Pinata procedures such as the above: do magic steps I discovered through trial and error that I don't understand until the candy falls out.

Additional context

Latest vscode scala metals plugin v 1.60.0

Search terms

semanticdb

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions