Support wildcards in resolve directives #817
Labels
Comments
|
Hey, any update on this issue? |
DolceTriade
added a commit
to DolceTriade/bazel-gazelle
that referenced
this issue
May 23, 2023
Similar to the resolve directive, resolve_regexp will match the import string against a regex instead of a direct string match. This is useful when matching protos which are part of single rule. Fixes bazel-contrib#817
DolceTriade
added a commit
to DolceTriade/bazel-gazelle
that referenced
this issue
May 25, 2023
Similar to the resolve directive, resolve_regexp will match the import string against a regex instead of a direct string match. This is useful when matching protos which are part of single rule. Fixes bazel-contrib#817
DolceTriade
added a commit
to DolceTriade/bazel-gazelle
that referenced
this issue
Jun 21, 2023
Similar to the resolve directive, resolve_regexp will match the import string against a regex instead of a direct string match. This is useful when matching protos which are part of single rule. Fixes bazel-contrib#817
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This came up in discussion in #771.
Currently,
resolvedirectives have two forms:We currently don't support any form of wildcard, so if a repository needs to use
resolvedirectives for a large number of rules (for example, when using a custom naming convention or a large number of rules in a directory), it needs a large number ofresolvedirectives, which can be very repetitively.We should support some sort of wildcard in the
import-stringwhich could also appear in thedep-string. The simplest and most familiar way to do this would probably be to introduce aresolve_regexpdirective, whereimport-stringis a regular expression, anddep-stringis something that could be passed toregexp.ReplaceAll(with$1and so on for matched groups).The text was updated successfully, but these errors were encountered: