-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle the removal of to_proto and to_json from struct #1554
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @c-mita!
Test failures appear unrelated to my changes. |
Check that the names exist before trying to remove them from the list of fields on a struct. These methods do not exist if --incompatible_struct_has_no_methods is passed or if they have been removed in a future version of Bazel.
Can we make a new release with this change to unblock migrating other projects bazelbuild/rules_webtesting#475 (comment) |
Hi, @sgowroji, just made a new release including this change https://github.com/bazelbuild/rules_scala/releases/tag/v6.5.0 |
Details: - https://github.com/bazelbuild/rules_scala/releases/tag/v6.5.0 Removes the part of the patch that worked around the removal of `to_proto` and `to_json` members from a struct, since this version contains a fix: - bazelbuild/rules_scala#1554 Updates the remaining part of the patch to define `_unmangle_bzlmod_repo_name`. This is in anticipation of the Bazel maintainers replacing `~` as the canonical repo name format delimiter due to build performance issues on Windows: - bazelbuild/bazel#22865 Signed-off-by: Mike Bland <mbland@engflow.com>
Details: - https://github.com/bazelbuild/rules_scala/releases/tag/v6.5.0 Removes the part of the patch that worked around the removal of `to_proto` and `to_json` members from a struct, since this version contains a fix: - bazelbuild/rules_scala#1554 Updates the remaining part of the patch to define `_unmangle_bzlmod_repo_name`. This is in anticipation of the Bazel maintainers replacing `~` as the canonical repo name format delimiter due to build performance issues on Windows: - bazelbuild/bazel#22865 I plan to see about contributing this function to bazelbuild/bazel-skylib eventually. Signed-off-by: Mike Bland <mbland@engflow.com>
Check that the names exist before trying to remove them from the list of fields on a struct.
These methods do not exist if --incompatible_struct_has_no_methods is passed or if they
have been removed in a future version of Bazel.