Skip to content

Proposal: ability to detect set/unset fields by client #101

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

Open
boukeversteegh opened this issue Jul 4, 2020 · 0 comments
Open

Proposal: ability to detect set/unset fields by client #101

boukeversteegh opened this issue Jul 4, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request low priority medium priority medium Medium effort issue, can fit in a single PR
Milestone

Comments

@boukeversteegh
Copy link
Collaborator

This idea has been brought up a few times.

Clients want to know whether an object they've created has a certain field explicitly set or not (even when it was set to the default).

This is different from detecting whether the field was set on the wire, since it is not distinguishable whether a default value was set, or that it was omitted.

We would need this feature internally to fix #74, and for #95.

A discussion about this is available on our Slack at #unset-field-detection. In due time, the content there should be consolidated here on github.

@boukeversteegh boukeversteegh added enhancement New feature or request large Large effort issue, multiple PRs, needs to be split up medium Medium effort issue, can fit in a single PR and removed large Large effort issue, multiple PRs, needs to be split up labels Jul 4, 2020
@boukeversteegh boukeversteegh added this to the Better Fields milestone Jul 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low priority medium priority medium Medium effort issue, can fit in a single PR
Projects
None yet
Development

No branches or pull requests

4 participants