Unexpected text showed when the translated text in a split has the same value as the default language text in that split

Actually my second idea seemed easier to do: if a config exists by default (in sync) but not when the split is active, we config-split:export that config as an empty array yaml file. Then on config import, we delete this config if it exists, in case we detect an empty array.

I made some manual testing, for my use case but also for a "normal" config entity (not a translation one). It seems to work well. But I would not be surprised if my code has problems I did not expect. This code seems complex to me and I think it's the first time I contribute to it. I was not always sure of the meaning of every line, some where sort-of copy-pasted.

Anyway, I made a merge request. But even if the idea is OK and the implementation is OK too, I guess tests would be needed?

The good news is that this would give a new feature: remove a config only in a split.

we should definitely have a test for that! It would help me step through the code and find more edge cases.

Hello bircher, I made tests and added some comments to the MR.

The MR now has conflicts with the latest 2.0.x.

I resolved the conflicts but now tests are failing.

I rebased on 2.0.x and tests are fixed.