- Allow to suppress automatic Bazel project opening if .ijwb
or so …
#5208
+11
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…already exists by setting
bazel.project.auto.open.if.present
tofalse
.ijwb
or other model that corresponds to current Bazel project mode is present.Checklist
Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number:
<please reference the issue number or url here>
Description of this change
Currently, if there is
.ijwb
present Bazel plugin instructs IJ to open project and ignore the rest of models. This is happening because the very firstProjectOpenProcessor#isStrongProjectInfoHolder
is a winner and used to open the project.Registry key is introduced to have more control over Bazel project opening, and to allow to yield to other project models if they known(to the person who disbled Bazel default behavior) to be present.
Bazel has 2 project openers and there is also a change to not activate auto import if the model already present.