This repository was archived by the owner on Jul 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
This repository was archived by the owner on Jul 28, 2023. It is now read-only.
Tracking issue: Directives Hydration ⚛️ #64
Copy link
Copy link
Closed
Labels
Description
We are now actively working on the WordPress Directives Plugin Tracking issue instead ➡️
This issue aims to list and keep track of the tasks related to the Directives Hydration experiment.
For the Custom Elements Hydration experiment, please check the Tracking Issue: Custom Elements Hydration 🧩.
The main branch of this experiment is main-directives-hydration. Make sure you select it when opening a pull request if it is related to this experiment.
Please, proactively comment on this issue whenever you start working on a new task, get blocked, or finish a task, sharing as much detail and information as possible. Thanks!!
Experiments
- Experiment: Client-side navigation of the Query Loop block using directives gutenberg#44034
- Experiment: Client side navigations in the Product Query block woocommerce/woocommerce-blocks#7187
- Experiment: Replicate Navigation block using directives gutenberg#44509
- Benchmark for WP directives DAreRodz/js-framework-benchmark#1
Done
- ⚛️ Restructure the project folder and files to make it ready for the Directives Hydration #65
- ⚛️ Hydrate the blocks with Directives Hydration (using
wp-blockandwp-inner-blocks) #66 - ⚛️ Add directives to handle
providesContextandusesContext#68 - ⚛️ Add
SuspenseandErrorBoundaryexamples #70 - ⚛️ Fix hydration when there are scripts in the top of the body #71
- ⚛️ Get rid of the
<wp-block>wrapper #72 - ⚛️ Use a
wp-inner-blockattribute for each inner block #77 - ⚛️ Refactor directives and make them work inside client components #74
- ⚛️ Use
Suspenseandlazyto Hydrate views that were not registered before callinghydrate()#78
Next
On hold
Reactions are currently unavailable