Avoid false positives applying Google3 specific functionality to non-google3 specific bazel workspaces #49629
Labels
analyzer-package
Issues related to package:analyzer
area-analyzer
Use area-analyzer for Dart analyzer issues, including the analysis server and code completion.
P3
A lower priority bug or feature request
Related issue: #49544
The cherry pick was fine to unblock but I think the right solution to this is to stop treating non-g3 BAZEL workspaces as BAZEL workspaces as we don't really support that case anyway.
To detect g3 bazel workspaces we should check for the magic
dart/config/ide/flutter.json
file like the Flutter IntellIJ support does.
See
https://github.com/flutter/flutter-intellij/blob/e6bb872cca41d5bcdaebc073c6c6882f3fc22633/flutter-idea/src/io/flutter/bazel/Workspace.java#L34
That should avoid false positives like this and keep our different tools consistent.
The text was updated successfully, but these errors were encountered: