Skip to content

🔥Write truly safe and scalable Firestore Rules, Transpile Typescript to Security Rules!

License

Notifications You must be signed in to change notification settings

tylim88/FireLaw

Repository files navigation

Firelaw 烈火戒

Created by tylim88   License   dependency count   package size   github action   code coverage   GitHub issues   code coverage   Total alerts   Language grade: JavaScript

I decided to stop working on this project after I found out that the security rule methods does not support nested object well enough, the language has too much limitation.

Hence it is pointless to continue this project, there is no enough value.

You should be ok with read operations, because read rule is quite simple, but this is not the case with write operations.

My advice is to validate your data in cloud function instead, and use good libraries like yup, joi and zod.

You lose optimistic update in front end, but I think that is acceptable.

If you don't want keep the optimistic update, use trigger instead.

TLDR, Firestore security rule suck, don't use it with nested object.

Update

I will repurpose this library into VS Code extension that lint types of Firestore Security Rules based on Firelord type

About

🔥Write truly safe and scalable Firestore Rules, Transpile Typescript to Security Rules!

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published