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
I understand that this might not be firebase/emberfire-related but has more to do with the way ember works and what its assumptions about backends are.
I still would like to point out this behaviour.
I have a path where users are allowed to create data, but are NOT allowed to read, delete or update that data.
When saving entities in ember, that also causes a GET-Request to receive the state of the newly saved data. That totally makes sense because very often you will find the backend to be adding/updating some attributes. However, when read-access is not granted, this still should not throw an error.
The runtime-error that is thrown is:
firebase.js:186 Error: permission_denied at [...]: Client doesn't have permission to access the desired data.
Version info
e.g.
DEBUG: -------------------------------
DEBUG: Ember : 2.5.0
DEBUG: Ember Data : 2.5.0
DEBUG: Firebase : 3.0.0
DEBUG: EmberFire : 2.0.0
DEBUG: -------------------------------
The text was updated successfully, but these errors were encountered:
Hey!
I understand that this might not be firebase/emberfire-related but has more to do with the way ember works and what its assumptions about backends are.
I still would like to point out this behaviour.
I have a path where users are allowed to create data, but are NOT allowed to read, delete or update that data.
When saving entities in ember, that also causes a GET-Request to receive the state of the newly saved data. That totally makes sense because very often you will find the backend to be adding/updating some attributes. However, when read-access is not granted, this still should not throw an error.
The runtime-error that is thrown is:
Version info
The text was updated successfully, but these errors were encountered: