You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
Currently, Sourcegraph does not support precise code intelligence for Protobuf files. We have validated an approach to accomplish this in a way so that cross-language navigation between *.proto files and the generated Protobuf files works as well. This means that "Go to definition" from Go/Java programs will be able to jump to the original *.proto file instead of the generated programs. Likewise, "Find references" on Protobuf symbols will be able to show usages from Go/Java programs.
The approach we have validated works by post-processing the generated LSIF files from lsif-go and lsif-java. Currrently, post-processing LSIF is quite awkward so we're investigating solutions to improve that before shipping Protobuf support.
The approach we have validated works by post-processing the generated LSIF files from lsif-go and lsif-java. Currrently, post-processing LSIF is quite awkward so we're investigating solutions to improve that before shipping Protobuf support.
Currently, Sourcegraph does not support precise code intelligence for Protobuf files. We have validated an approach to accomplish this in a way so that cross-language navigation between
*.proto
files and the generated Protobuf files works as well. This means that "Go to definition" from Go/Java programs will be able to jump to the original*.proto
file instead of the generated programs. Likewise, "Find references" on Protobuf symbols will be able to show usages from Go/Java programs.The approach we have validated works by post-processing the generated LSIF files from lsif-go and lsif-java. Currrently, post-processing LSIF is quite awkward so we're investigating solutions to improve that before shipping Protobuf support.
The text was updated successfully, but these errors were encountered: