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

Feature / Updated null behaviour (TS, --force-message, properties and members) #2013

Conversation

martin-traverse
Copy link
Contributor

This relates to #2012

See also discussion around proto3 optional fields, issue #1779 PR #2011

@martin-traverse
Copy link
Contributor Author

See #2011, it may be simpler to bring these changes into that one PR using a single guard flag, --null-semantics.

@martin-traverse
Copy link
Contributor Author

Closing as this is now fully covered by PR #2011

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.

1 participant