You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a need to show post type and taxonomy labels in the Gutenberg interface. This will enhance the experience of related workflows such as "Add New Genre" (for a genre custom taxonomy) in place of the generic "Add New Tag".
Potentially, this ties into a larger need for sharing localized strings between the server and client, but in these cases the strings are very dynamic (depending on which post types / taxonomies registered).
Potential solutions may include bootstrapping localized strings from the server using wp_localize_script, but it opens concerns of:
How scalable is this approach for increasingly client-based interfaces? Media library strings are the closest example and are already quite unwieldy.
What solution is there for interfaces consuming from the REST API which don't have the option to bootstrap from the server (e.g. static single-page applications)?
The text was updated successfully, but these errors were encountered:
Related: #2489 (comment)
Relevant APIs:
Prior art:
There's a need to show post type and taxonomy labels in the Gutenberg interface. This will enhance the experience of related workflows such as "Add New Genre" (for a genre custom taxonomy) in place of the generic "Add New Tag".
Potentially, this ties into a larger need for sharing localized strings between the server and client, but in these cases the strings are very dynamic (depending on which post types / taxonomies registered).
Potential solutions may include bootstrapping localized strings from the server using
wp_localize_script
, but it opens concerns of:The text was updated successfully, but these errors were encountered: