How to contribute to this issue:

• Scroll down below to check the existing PRs so you don't open a PR for a component waiting for review
• Refactor components based on the description below - also check the guidelines for PRs
• Reference this issue with #58 in the PR description so we can track which component

I looks like, at the moment, if I want to write many records at once, I have to either do a series of individual document writes. Or I have to write all the records to a single doc. It would be great to be able to create and write out to many docs simultaneously and atomically.

Fireorm supports validation by leveraging the responsibility to class-validator. To perform the validation we have to declare a function on each abstract repositories like (this one or [this one](https://github.com/wovalle/fireorm/blob/dd10d7d52441894c4701a085d4

Is your feature request related to a problem? Please describe.
I'd like to be able to A/B test my games through Firebase and have them be tracked and what not, as well as updated and experimented on so I can come up with the best possible results.

Describe the solution you'd like
Simply put, I'd like RemoteConfig to be implemented so I can utilize it to implement the A/B testing. That

Feature request

• Extension name: firestore-stripe-payments

Is your feature request related to a problem? Please describe.

I would like to create a way for my customers to automatically redeem a coupon intended only for a specific customer group. Currently you can only specify a promotion_code when creating a checkout session.

Describe the solution you'd like

It would be

Hello,

Thanks for this awesome tool!

I have a guarded property on my store, selected, which is used only by the UI, and I don't want to sync on Firestore.
If the guards works well, the document is still synced everytime I change the selected value, because of the updated_at and updated_by value.
Of course, I can add the two properties to the guards too, and it works, but I actually

I was hoping to be able to delete multiple documents at once.

For v0: Each new version push should trigger npm run docs admin.
For v1 and above: Each new major/minor version push should trigger npm run docs admin.

The generated docs should be committed with the following message Docs for {versionString}.