- 🇨🇦Canada arakwar
Adding the 'langcode' elekment there does work in hiding the langcode change, but still imports those changes in the website. So this would only be a UI fix for now.
I wonder how complex it would be to apply an existing translation on top of a configuration before importing it. Like, if my feature has English as a base and French as a translation, but the target site is in French as a base, then applying the French translation of config on the import could make sense.
But it feels like a huge change...