Skip to content
This repository was archived by the owner on May 26, 2022. It is now read-only.

Document update mutation behavior for temporal and spatial types #43

Open
johnymontana opened this issue Jun 10, 2020 · 0 comments
Open

Comments

@johnymontana
Copy link
Contributor

Make it clear that update and merge mutations replace the value of the temporal and spatial properties, which means all components of a DateTime (for example) must be provided, not just the components intended to be updated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant