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
There are some forbidden field names , that cause errors, unexpected behavior. For example if i use 'className' in object data type
set{"className","something"} the resulted return object wouldnt be a jsonObject as expected , rather a parse object, cousing cast errors. It would be good including the forbidden field names in docs.
The text was updated successfully, but these errors were encountered:
Are you referring to the SDK or to Parse Server? If SDK, how do other Parse client SDKs handle this? If Parse Server, it should reject an invalid / reserved field name. It does so with other invalid names, so this should be added to the internal list.
There are some forbidden field names , that cause errors, unexpected behavior. For example if i use 'className' in object data type
set{"className","something"} the resulted return object wouldnt be a jsonObject as expected , rather a parse object, cousing cast errors. It would be good including the forbidden field names in docs.
The text was updated successfully, but these errors were encountered: