alexklibisz / firebak Goto Github PK

The Blaze (https://github.com/firebase/blaze_compiler) and Bolt (https://github.com/firebase/bolt) compilers are arguably a more efficient way to write your Firebase rules once you hit a certain level of complexity.

I've recently re-written our rules using the Blaze compiler, and I noticed that doing the no-op comment to define a sharding variable for firebak doesn't work anymore.

e.g. this can't be achieved in Blaze:

"firebak:shard:100": {}

so another option I was thinking of is to allow the rule to live in the indexOn property:

e.g.:

indexOn: ["oneKey", "anotherKey", "firebak:shard:100"]

I'll likely prototype it out within the week as we migrate the new Blaze-based rules into production. Any thoughts on this approach are welcome.

when I try to restore I got this
Firebase.child failed: First argument was an invalid path: "tub/-KFhK6z8yR9MQzAi-V_e/-KLpLpG0yYFOKq0PjPrv/recent/16384f2a-2eaa-480a-81cc-b485e8d03e98/.priority". Paths must be non-empty strings and can't contain ".", "#", "$", "[", or "]"