Add scala_grpc_zio conflict resolver strategy #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Improve name parsing In a bazel package having multiple scala_library rules of the same package, there may be symbols that are not imported but still valid. For example, if "A.scala" has package "foo.bar" and defines class A, and "B.scala" defines class B extends A, "A" does not necessarily require an import if they are both in the package "foo". However, the rule "b_scala" needs "a_scala" in its deps. How to determine that? This is accomplished by running the resolve action twice. The first time the scopes are populated, and the second time, we can use the "gazelle:resolve_file_symbol_name" directive to try and autopopulate imports based on completion of symbols in the "Names" file metadata.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.