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
In rules_docker we are addressing issue #7347 to only return a list of providers from all rule implementation functions (PR). We import the file_test rule from this project that still returns a struct, which makes our CI fail when running with the --incompatible_disallow_struct_provider_syntax flag.
Do you have any timelines as of when you plan to address issue #7347 in this project or maybe for the file_test rule?
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run any file_testtarget with the --incompatible_disallow_struct_provider_syntax flag.
What's the output of bazel info release?
0.23.2
The text was updated successfully, but these errors were encountered:
Description of the problem / feature request:
In rules_docker we are addressing issue #7347 to only return a list of providers from all rule implementation functions (PR). We import the
file_test
rule from this project that still returns a struct, which makes our CI fail when running with the--incompatible_disallow_struct_provider_syntax
flag.Do you have any timelines as of when you plan to address issue #7347 in this project or maybe for the
file_test
rule?Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run any
file_test
target with the--incompatible_disallow_struct_provider_syntax
flag.What's the output of
bazel info release
?0.23.2
The text was updated successfully, but these errors were encountered: