Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upProposal: ability to detect set/unset fields by client #101
Assignees
Projects
Milestone
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.