SemanticDB Generation (gives find references) about bazel-bsp HOT 10 CLOSED

For Bloop we send extra data, maybe we could reuse that approach here?

It would seem reasonable to use the same approach so that there doesn't need to be additional special casing on the client side.

from bazel-bsp.

one more scala_rules change!

from bazel-bsp.

This would be very useful to fully support Bazel in Metals, do you have any idea how we can achieve it? For Bloop we send extra data, maybe we could reuse that approach here?

from bazel-bsp.

for now i haven't thought about it yet. If this is important to you, I will try to start working on it in the near future

from bazel-bsp.

for now i haven't thought about it yet. If this is important to you, I will try to start working on it in the near future

It would be really useful, but I don't want to put any pressure on you. Maybe with some pointers we could try to figure it out ourselves?

from bazel-bsp.

for now i haven't thought about it yet. If this is important to you, I will try to start working on it in the near future

It would be really useful, but I don't want to put any pressure on you. Maybe with some pointers we could try to figure it out ourselves?

If you have any questions, I will try to answer them. Right now I'm focusing on another project, so it will probably be faster for you to add this support on your own

from bazel-bsp.

Is it possible to produce SemanticDB without altering already existing WORKSPACE/BUILD/rules definitions? If I understand correctly, bazel-bsp is an abstraction over bazel and under the hood it invokes bazel commands so it seems like we cannot do much more than is defined in build config files.

from bazel-bsp.

Is it possible to produce SemanticDB without altering already existing WORKSPACE/BUILD/rules definitions?

I'm not very familiar with semanticDB in general, so it's a little hard to answer this question

If I understand correctly, bazel-bsp is an abstraction over bazel and under the hood it invokes bazel commands so it seems like we cannot do much more than is defined in build config files.

yes, indeed - bazel bsp invokes bazel and collects information from the response + BEP events. So, it is possible to obtain any information as long as bazel is able to response with it

from bazel-bsp.

AFAIK, this issue cannot be resolved without changes in scala_rules, see bazelbuild/rules_scala#952

from bazel-bsp.

moved to: https://youtrack.jetbrains.com/issue/BAZEL-38

from bazel-bsp.