Skip to content
This repository was archived by the owner on Jul 28, 2023. It is now read-only.
This repository was archived by the owner on Jul 28, 2023. It is now read-only.

Tracking Issue: Server-side rendering of directivesΒ #120

@ockham

Description

@ockham

Based on #118 (comment) and #125.

βœ… - Implemented
🟑 - Waiting for an upcoming Gutenberg release to include a missing feature
❌ - Blocked by missing feature in WP_HTML_Tag_Processor

Name Directive Missing feature
wp-context βœ… (#143)
wp-show 🚧 (#141) Wrapping content inside HTML tags with extra tags. E.g. get_content_inside_balanced_tags() from WordPress/gutenberg#46345, and a matching set_content_inside_balanced_tags() (see WordPress/gutenberg#47036).
wp-bind βœ… (#133) get_attribute_names_with_prefix(); landed in GB 15.0
wp-class βœ… (#133) See wp-bind.
wp-style βœ… (#133) See wp-bind. Furthermore, see WordPress/gutenberg#46887. (The latter isn't a blocker, though.)
wp-text βœ… (#170) Replace content between HTML tags. See wp-show.
wp-for / wp-each 🚧 (#166)
wp-html βœ… (#170) Replace content between HTML tags. See wp-show.
wp-slot & wp-fill

TODO:

  • Properly parse expressions in attributes like when.
    • Includes nested JS-style objects (e.g. context.myblock.open).
    • Basic logic operations (negation, and, or)? Comparison?
  • Add some directive/components registration mechanism.
    • Maybe similar to blocks, patterns, etc? register_directive, takes a directory with a directive.json which includes information such as attributes, render, context, ...?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions