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
Manually editing the source roots via the context menu by clicking on a folder in the Project view and selecting "Mark Directory As -> Sources Root" is discarded on each IntelliJ Bazel plugin Sync.
For Python files and targets, this means their source roots are never detected and cannot be persisted between IntelliJ Bazel plugin Syncs.
Source root detection doesn't appear to work even for Java files in some cases : #1992
I can think of a few different paths to address this problem:
Stop automatically setting source roots on each Sync. Force them to be manually configured like a regular IntelliJ project.
Maybe still allow automatic detection only on the first IntelliJ project import?
Allow manual configurations via IntelliJ's menus to work as an override that persists through syncs.
Make a BUILD target / .bazelproject setting / etc. that flags a directory during Sync as a source root.
Refine the automatic detection logic so it can detect the correct source roots under a variety of scenarios including Python only directories
The text was updated successfully, but these errors were encountered:
The Bazel IntelliJ plugin appears to detect IntelliJ project source roots by the presence of specific Java centric identifiers.
https://github.com/bazelbuild/intellij/blob/master/java/src/com/google/idea/blaze/java/sync/source/SourceDirectoryCalculator.java
Manually editing the source roots via the context menu by clicking on a folder in the Project view and selecting "Mark Directory As -> Sources Root" is discarded on each IntelliJ Bazel plugin Sync.
For Python files and targets, this means their source roots are never detected and cannot be persisted between IntelliJ Bazel plugin Syncs.
Source root detection doesn't appear to work even for Java files in some cases : #1992
I can think of a few different paths to address this problem:
The text was updated successfully, but these errors were encountered: