Custom Field in Plugin produces i18n missing translation error.

[u382514]

Bug report

Describe the bug

I've created a simple plugin with a custom field called Subdomain. I've added this to the model directly from the backend since there doesn't seem to be a way to do that from the frontend. Getting back into Strapi and going to the collection under content-type builder will throw an error from I18n:

React Intl Error MISSING_TRANSLATION] Missing message: "content-type-builder.attribute.subdomain" for locale: "en"

I've tried adding the entry in the en.json file under translations however the issue still occurs.

Steps to reproduce the behavior

Create a custom field in a plugin and register the field. Add it to a collection model. Go to strapi admin and click on the collection under content-type builder. Watch the sparks fly in the console.

Expected behavior

I expect it to not do that. At the very least I'd expect that the entry in the en.json file should handle it, but preferably I'd like it to not error at all.

Screenshots

[soupette]

Custom fields are not supported (yet) in the content type builder. We have just made a fix so no error is displayed in the console for such case.