.exists() creates invalid Firebase rules
See original GitHub issueThe following Bolt rules:
path /some/$path {
validate() = root.items[$path].exists();
}
output the following invalid Firebase rules:
{
"rules": {
"some": {
"$path": {
".validate": "newData.parent().parent().child('items').child($path).child('exists')()"
}
}
}
}
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
exists() creates invalid Firebase rules · Issue #75 - GitHub
Output a warning if you try to use an unsupported method. Make an exception for .exists() - as it reads more explicitly than...
Read more >firestore rules get() / exists() not working - Stack Overflow
I am using Firestore rules and want to call get() / exist() in a function, and after that I call that function in...
Read more >Writing conditions for Cloud Firestore Security Rules - Firebase
Use security rules to write conditions that check user authentication, validate incoming data, or even access other parts of your database.
Read more >A List of Firestore Security Rules for Your Firebase Project
This is a list of simple and complex Firebase Security rules that you can use in your project today. I hope you will...
Read more >exists() function not finding any documents in Firestore ...
The create rule for the users collection is correct and the document is actually created. I can access its data and verify it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Don’t use child() in Bolt.
root,profiles[uid] != null
Is what you want.
On Sat, Jan 30, 2016, 7:14 PM Jake Mc notifications@github.com wrote:
#94 solved it for me
profileExists(uid) { root.child(‘profiles’).child(uid).val() != null }