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
With this previous issue, a breaking change with the protobuf-gradle-plugin and bug was fixed to remove linting/formatting of generated code.
That fix addressed issues of performing linting of proto files imported from other dependencies. However, it turns out that the protobuf-gradle-plugin will generate multiple build-extracted/protos/... directories when non-main-source-set configurations are used (e.g. testImplementation(<some GAV>)).
This results in the weird broken behavior similar to the previous issue.
I'll put together what I believe to be a straightforward fix that removes the build-extracted--protos- prefixed directories from the set of sources that need to be linted.
The text was updated successfully, but these errors were encountered:
With this previous issue, a breaking change with the
protobuf-gradle-plugin
and bug was fixed to remove linting/formatting of generated code.That fix addressed issues of performing linting of proto files imported from other dependencies. However, it turns out that the
protobuf-gradle-plugin
will generate multiplebuild-extracted/protos/...
directories when non-main-source-set configurations are used (e.g.testImplementation(<some GAV>)
).This results in the weird broken behavior similar to the previous issue.
I'll put together what I believe to be a straightforward fix that removes the
build-extracted--protos-
prefixed directories from the set of sources that need to be linted.The text was updated successfully, but these errors were encountered: