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

Default protoencoding resolver to an empty resolver #3345

Merged
merged 2 commits into from
Sep 26, 2024
Merged

Conversation

emcfarlane
Copy link
Contributor

This changes the behaviour of protoencoding to always set a resolver on init, defaulting to the protoencoding.EmtpyResolver. Currently, Marshaller and Unmarshallers will default to the protoregistry.GlobalTypes if a nil resolver is set. To keep the same behaviour the caller must pass in the GlobalTypes explicitly.

This changes the behaviour of protoencoding to always set a resolver on
init. Marshaller and Unmarshallers will default to the
protoregistry.GlobalTypes if a nil resvoler is passed in. To keep the
same behaviour the caller must pass in the GlobalTypes explicitly.
Copy link
Contributor

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedSep 26, 2024, 3:04 PM

Copy link
Member

@bufdev bufdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me, but I'd verify that this doesn't bork anything in core.

@bufdev bufdev merged commit c851732 into main Sep 26, 2024
13 checks passed
@bufdev bufdev deleted the ed/defaultToEmpty branch September 26, 2024 17:03
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.

3 participants