Skip to content
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

Make anyTranscodeFailure more descriptive (1.x branch) #1530

Closed

Conversation

rebello95
Copy link
Contributor

Right now it's quite difficult to identify which type is missing from the Google_Protobuf_Any registry when the anyTranscodeFailure is thrown without having Xcode and breakpoints to debug the program. This change makes the error more descriptive and actionable by including the type URL that needs to be registered.

This is a mirror of #1527 targeting the 1.x branch.

Right now it's quite difficult to identify _which type_ is missing from the `Google_Protobuf_Any` registry when the `anyTranscodeFailure` is thrown without having Xcode and breakpoints to debug the program. This change makes the error more descriptive and actionable by including the type URL that needs to be registered.
@thomasvl
Copy link
Collaborator

thomasvl commented Jan 2, 2024

This is a mirror of #1527 targeting the 1.x branch.

I don't think we'll be able to accept then one, as it likely would count as breaking change, so it can only live on the 2.x branch because of that.

@tbkka thoughts?

@thomasvl thomasvl changed the title Make anyTranscodeFailure more descriptive Make anyTranscodeFailure more descriptive (1.x branch) Jan 2, 2024
@thomasvl
Copy link
Collaborator

thomasvl commented Jan 3, 2024

Closing this since it is an api change per @tbkka's #1527 (comment)

@thomasvl thomasvl closed this Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants