Repository navigation
Report *.mill files as "wrapped sources" via BSP - #6874
Conversation
|
I can't find the BSP spec of the
I still don't get it, why the Scala-CLI developers never tried to upstream the request. This is not at all how Open Sources works. The current state of the BSP project is unmaintained and the repo is kind-of unmaintainable. But I still would prefer to upstream the wrappedSources request into the spec. Maybe we can just fork the BSP project from its last stable release tag, which should be still on sbt? Or we can just take maintainership, revert the Bazel migration and add the wrappedSources request directly? |
Conflicts: runner/meta/src/mill/meta/MillBuildRootModule.scala
|
This change makes |
I don't know, editing |
Co-authored-by: Tobias Roeser <le.petit.fou@web.de>
This makes Mill report its
*.millfiles as "wrapped sources" in BSP via thebuildTarget/wrappedSourcesrequest. This can help BSP clients pass to their presentation compiler the same sources that Mill passes to the compiler. In order to get more accurate infos from it, in particular for thebuild.*stuff in the build (to refer to things defined in other*.millfiles).Quick tests on a minimal project show that this doesn't break the currently existing features in Metals, while I can make good use of it in my own LSP server.
Pull request: #6874