Interactivity API: Support setting a namespace using a string in data-wp-interactive

[luisherranz]

What?

Support setting a namespace using a string in data-wp-interactive, like data-wp-intearctive="myPlugin".

Why?

Because the namespace is the main and only property supported now, so it makes sense to allow it, instead of the longer data-wp-interactive='{ "namespace": "myPlugin" }' form.

How?

By checking if the attribute value of data-wp-intearctive is a string, and if it is, using it as the namespace.

---

In the server, string namespaces are supported in this WP Core PR:

• Interactivity API: Server Directive Processing wordpress-develop#5953
• WordPress/wordpress-develop@6345e24

Be aware that here in Gutenberg this will be supported once the PR is committed to WP Core and the code is synced back to Gutenberg.

---

Co-authored with @sirreal.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core SVN

Core Committers: Use this line as a base for the props when committing in SVN:

Props luisherranz, darerodz.

GitHub Merge commits

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: luisherranz <[email protected]>
Co-authored-by: DAreRodz <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[luisherranz]

I've added again the namespace restrictions because as @DAreRodz pointed out, things that contain :: could fail, like { "text": "Hi :: there!" } or "Hi :: there!".

I'll apply the same restrictions in the server directive processing.

[DAreRodz]

LGTM!

PS: I guess have to update the namespaces from objects to strings in core blocks, right? We can do so in a different PR, don't worry. 😄

[luisherranz]

It's not strictly required because both are supported, but yeah, it'd be nice.