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
This is a follow-up to the closed issue #6458 regarding the limitations and handling of protectedFields in Parse Server.
Current Behavior:
protectedFields hides fields during get/find but allows create/update to modify them.
Users can currently add constraints using protected fields in queries, which may bypass protection unintentionally.
Proposals:
Introduce a stricter error-throwing mechanism when protected fields are involved in mutations.
Provide a way to enforce constraints dynamically based on pointer fields in queries.
Description:
This is a follow-up to the closed issue #6458 regarding the limitations and handling of protectedFields in Parse Server.
Current Behavior:
protectedFields hides fields during get/find but allows create/update to modify them.
Users can currently add constraints using protected fields in queries, which may bypass protection unintentionally.
Proposals:
Introduce a stricter error-throwing mechanism when protected fields are involved in mutations.
Provide a way to enforce constraints dynamically based on pointer fields in queries.
Link to original issue: #6458
Thank you!
The text was updated successfully, but these errors were encountered: