-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Datastore: empty lists are not reflected in 'client.put' #6284
Comments
@tseaver That's not where the logic was added, it just moved. ISTM that de03993 is the correct place
As for this issue, does #6285 actually fix it? That is, does the backend distinguish between empty and unset? |
The backend very much does. If unset comes on the first one the column isn't even there. We don't send it. (which is the reason for removing the check so it would add the empty instance) It is also graphically different in the portal. not set is '-' where empty array is '[]' |
* Fix #6284 by handling empty arrays in entity to pb
Related to #3767
Currently, Sending an empty array results in the field not being set.
Output:
The text was updated successfully, but these errors were encountered: