Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`init` should not change database security rules
See original GitHub issueI have an existing Firebase app that I upgraded to the new console. Then in an empty folder I ran firebase init and completed the prompts. In the end, I get a database.rules.json file with globally read-write enable rules.
{ ".read": true, ".write": true }
But I actually have configured more restrictive security rules from the old console. Those rules are still present in the new console. I think the init command should use existing security rules for an app. Please look into this.
Thanks.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jobsamuel great ideas here! Could you submit the rollback feature as a separate request?
The pull request has now been merged into Master (see above). @TamalSaha let me know if this addresses concerns that you have, and whether there are unresolved concerns that would warrant another issue.