My suggestion is that if the property doesn't exist it should just be considered a successful operation. Current behaviour is that it throws.
If by doing a remove operation you only care that the property doesn't exist anymore, the fact that it doesn't exist to start with should just tell you it was a success anyway.
And I guess when there are like 10 operations going, you don't want all the other operations to be cancelled for one remove that couldn't find a property.
To solve this and not change the current behaviour, maybe adding an option like successRemoveUnexisting: true that you can turn on if that's how you want it to behave?
My suggestion is that if the property doesn't exist it should just be considered a successful operation. Current behaviour is that it throws.
If by doing a remove operation you only care that the property doesn't exist anymore, the fact that it doesn't exist to start with should just tell you it was a success anyway.
And I guess when there are like 10 operations going, you don't want all the other operations to be cancelled for one remove that couldn't find a property.
To solve this and not change the current behaviour, maybe adding an option like
successRemoveUnexisting: truethat you can turn on if that's how you want it to behave?