This has happened too many times: We do an replace update, but mapping to a twig template. The CSV has only the keys we want to replace but because all is mediated by a template the template itself generates new empty keys that end replacing good metadata we don't want.
A simple extra (IN BOLD) notice for the two replacement modes warning people about that, will (hopefully) make everyone think twice before applying a template blindly! And save many revisions to us/everyone.
What?
This has happened too many times: We do an replace update, but mapping to a twig template. The CSV has only the keys we want to replace but because all is mediated by a template the template itself generates new empty keys that end replacing good metadata we don't want.
A simple extra (IN BOLD) notice for the two replacement modes warning people about that, will (hopefully) make everyone think twice before applying a template blindly! And save many revisions to us/everyone.