Documentation Update: Firebase-Counter Deletes Subcollection/Shards Once Aggregated about extensions HOT 6 CLOSED

Hi @tommyc38 thanks for opening the issue. Although this intended, I do think it would be best to let users know about this, to ensure they are only using the "master" counter.

@rachelsaunders would this be best placed here or do you think it requires an explanation within the PREINSTALL doc?

from extensions.

For clarification - does the extension delete the subcollections each time the scheduled function runs?

from extensions.

@rachelsaunders, either I am experiencing a bug or it does indeed delete the sub collection if it has no more shards (docs) to count. Assuming this is intended, having a line or two about this in the docs will be helpful to others who run tests and expect to see a sub collection but don't.

from extensions.

@Ehesp Friendly ping on my clarification question above? Thx!

from extensions.

Hi @rachelsaunders - it deletes them once they have been aggregated yes. Users should sync with the 'master' doc created, as it's unreliable to sync with the aggregators (as they can be removed anytime).

from extensions.

closed w/ merge of PR #62

from extensions.