-
Notifications
You must be signed in to change notification settings - Fork 34
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
Cannot drop a record property #378
Labels
Comments
n1k0
added a commit
that referenced
this issue
Jan 31, 2017
n1k0
added a commit
that referenced
this issue
Feb 1, 2017
n1k0
added a commit
that referenced
this issue
Feb 2, 2017
Fixed by #379. |
n1k0
added a commit
that referenced
this issue
Feb 16, 2017
New features * Fix #377, #378: Allow dropping edited resource properties. (#379) * Fix #365: Render a JSON diff for history entries. (#380) * Fix #376: Denote readonly buckets & collections in the sidebar. (#382) * Fix #384: Live-searchable/filterable sidebar entries. (#385) * Hide auth method selector when a single one is configured. Bugfixes * Do not store passwords. Fixes #364 (#386)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because we perform PATCH requests, the sent record payload is always merged with its server version, so the property value always remains.
We could merge form values into initial record object when sending the request.As patching is only required for collection attributes, so we don't lose attributes not handled by the edit form, we should:
patch
option for updating buckets, groups and records (so we always replace records);Spawned from #377.
The text was updated successfully, but these errors were encountered: