You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fields with an array type are always returned as arrays. Even when they have not been set. This causes conflicts between raw and derived datasets. E.g., downloading a raw dataset returns
inputDatasets= []
usedSoftware= []
These fields are not allowed for raw datasets. So this can cause validation errors in clients. See, e.g., SciCatProject/scitacean#226.
Similarly, other array fields such as relationships and sharedWith are returned as [] even if they have not been set during upload.
Is this intended behaviour? Should clients treat empty arrays equivalently to absent / none fields?
The text was updated successfully, but these errors were encountered:
Fields with an array type are always returned as arrays. Even when they have not been set. This causes conflicts between raw and derived datasets. E.g., downloading a raw dataset returns
These fields are not allowed for raw datasets. So this can cause validation errors in clients. See, e.g., SciCatProject/scitacean#226.
Similarly, other array fields such as
relationships
andsharedWith
are returned as[]
even if they have not been set during upload.Is this intended behaviour? Should clients treat empty arrays equivalently to absent /
none
fields?The text was updated successfully, but these errors were encountered: