Follow-up to https://github.com/backdrop/backdrop/pull/2397#discussion_r244554774
Because we have both $active_config and $staging_config, and you've passed in $context above... we could delete the out-of-date strings that are no longer used from the locale table when a string changes. For example if the translation for the registration email changes (or the content of the registration email changes), we don't need to be keeping all the old copies of that translated string in the database, just delete them all with that context key.
GitHub Issue #:
3452
Recent comments
Yes, if you don't have acidfree and gedcom as content types they will be safe to delete.
taxonomyextra table after migration from Drupal 6
@yorkshirepudding Thanks for that bit of information. I checked and this is what was found: There were several json files in the active folder: field.field.taxonomyextra.json...
taxonomyextra table after migration from Drupal 6
To confirm that it is ok to be deleted, I would look in the config folder for any config files with the string taxonomyextra in. If you don't find any, then yet it is probably safe to drop...
taxonomyextra table after migration from Drupal 6