I have a custom Class called
Item. I would like to use Parse’s auto-generated
createItem GraphQL mutation to add an item for the currently logged in user.
I have my
Item class security set as follows:
- CLP: Public Read/Write is disabled; Authenticated Read/Write is disabled; a
userfield is set.
- ACL: Not applicable for a
For security reasons, I don’t wish to open my
Item class to
Public or generic
Authenticated access, so my
createItem mutation is failing at the CLP level. Under the circumstances, it feels like my only alternative is to not use the
createItem mutation and to instead create a custom schema mutation with a Cloud Code resolver that bypasses my CLP security via use of the
My question is this… Is there is another way around this situation so that I can use the built-in
createItem mutation as desired?