Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upincompatible_disable_legacy_proto_provider: Remove legacy `dep.proto.` access to the proto provider #7152
Comments
lberki
added
team-Rules-Server
incompatible-change
migration-ready
migration-0.22
breaking-change-0.23
labels
Jan 17, 2019
dslomov
removed
the
migration-ready
label
Jan 31, 2019
This comment has been minimized.
This comment has been minimized.
This flag was not flipped in time for the Bazel 0.23.0 release and will thus be postponed to Bazel 0.24.0. |
philwo
added
breaking-change-0.24
migration-0.23
and removed
breaking-change-0.23
labels
Feb 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lberki commentedJan 17, 2019
We are migrating off of legacy providers that are addressed by name to providers addressed: https://bazel.build/designs/skylark/declared-providers.html
This bug is for migrating the provider containing information about
.proto
files. The following changes are required in Starlark sources:ctx.attr.dep.proto.
toctx.attr.dep[ProtoInfo]
hasattr(dep, "proto")
toProtoInfo in dep
providers = [["proto"]]
toproviders = [[ProtoInfo]]