[go: nahoru, domu]

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

Place the right Security Rules back! #46

Closed
akauppi opened this issue Apr 15, 2021 · 2 comments
Closed

Place the right Security Rules back! #46

akauppi opened this issue Apr 15, 2021 · 2 comments
Assignees
Labels
bug Something isn't working proxy Points to a third party issue

Comments

@akauppi
Copy link
Owner
akauppi commented Apr 15, 2021

Once firebase/firebase-js-sdk#4795 is resolved, change this back:

      allow read: if true   // HACK! CHANGE! so that development can continue! AK 15-Apr-21
      //allow read: if isMember() && (!isRemoved() || isAuthor())
        //&& validProject2()       // optional: enable if you want to guard against bad data instead of letting client cope with it
@akauppi akauppi added bug Something isn't working proxy Points to a third party issue labels Apr 15, 2021
@akauppi akauppi self-assigned this Apr 15, 2021
@akauppi
Copy link
Owner Author
akauppi commented Apr 22, 2021

Sam Stern mentioned at firebase/firebase-tools#3258

Right now neither fix has been released but when the next JS SDK and Emulator release go out either fix should be sufficient to stop this issue from happening.

i.e. Firestore Emulator 1.11.15 should suffice

@akauppi
Copy link
Owner Author
akauppi commented May 24, 2021

done

@akauppi akauppi closed this as completed May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working proxy Points to a third party issue
Projects
None yet
Development

No branches or pull requests

1 participant