feat(sandbox): add support for language

[demetriusfeijoo]

What?

Allow the Sandbox user to pass a language to the plugin through postMessage.

Why?

JIRA: EXT-1812

It will allow users to test the language value and behavior of the field plugin.

Example of the new input on the mobile:

Example of the new input on the desktop:

When no language is informed:

When some language is informed:

How to test? (optional)

The sandbox/container, can be tested as described in our [CONTRIBUTING.md →]

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
plugin-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 25, 2023 5:38pm

[demetriusfeijoo]

The new input field is not in the footer since being close to the URL input field seemed more natural to me and I would like to collect your opinions on that.

So, what are your thoughts on that @johannes-lindgren @eunjae-lee ?

[eunjae-lee]

To me, the position of the input box seems good. What do you think? @johannes-lindgren

[johannes-lindgren]

To me, the position of the input box seems good. What do you think? @johannes-lindgren

I think it should be moved further down; to the content section.

The preview section contains the iframe and an input field for the iframe src attribute. I think all the data belongs to the other accordions. I think there should be more inputs added later, for

• content (currently not editable)
• story
• access token
• story id
• etc

[demetriusfeijoo]

Hey @johannes-lindgren, do you mean like that?

[johannes-lindgren]

Hey @johannes-lindgren, do you mean like that?

Yes, almost: below the JSON viewer, since the language input is less commonly used 🙂

When you develop a field plugin, you tend to use the options and the content JSON view the most.

[demetriusfeijoo]

Hey @johannes-lindgren, thanks for the comments and for guiding me through how to approach them. 🚀

Final result: