Dan Oved

I'm having this issue too

For me this is a critical part of my application - i use the firestore document as a state record for a user that is created when they open my...

I suppose a workaround is wrapping this `add` functionality in a cloud function that performs the adding, and the cloud function just returns the added element's id?

I need the id of the document, so I don't think try catching and swallowing it would work? For now I will wrap it in a cloud fn.

Wow, this is amazing, thanks so much! Can't wait to try this out.

I'm running into something similar. I want to create a test that: * creates a proxy contract with a deterministic address using create2 * deletes it then `selfdestruct`'s it *...

thanks to @onbjerg suggestion the behavior works as expectedly if `selfdestruct` is called in `setUp`: ```solidity /// @notice Meant to test out determistic cloning techniques contract DetermistingCloningTest is Test {...

I still have this issue, despite following the example.

+1

Yes this is correct. Feel free to submit a PR :)