Skip to content
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

Forbidden field names #1006

Open
visign3d opened this issue Aug 27, 2024 · 2 comments
Open

Forbidden field names #1006

visign3d opened this issue Aug 27, 2024 · 2 comments
Labels
type:docs Only change in the docs or README

Comments

@visign3d
Copy link

visign3d commented Aug 27, 2024

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.

Copy link

Thanks for opening this issue!

@mbfakourii mbfakourii added the type:docs Only change in the docs or README label Aug 27, 2024
@mtrezza
Copy link
Member

mtrezza commented Aug 28, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:docs Only change in the docs or README
Projects
None yet
Development

No branches or pull requests

3 participants