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
The aim of the development in Q1 is to resolve all beta & RC related issue, by either implementing or closing/moving the target date to another time, and go for an RC release at the end of the Q1 2024, or latest early Q2 2024.
A roadmap and an iteration plan will be provided & updated below for better clarity on the focus of the development.
🗺️ Roadmap
Main work to be completed during this time will be the final features that may require some "buffer" versions to stabilize the behavior, the bellow list comprises the significant ones (but not all):
migrate decorator to latest standard
event modifiers
remove build time shadow dom usage detection
element bindable should take priority over attribute
au compose synchronize behavior of custom element vs non, add support for string
element bindable spread syntax
form actionless behavior on par with v1
simplify metadata
static resources registration
closest parent attribute
auto infer binding expression
import[as] in convention plugin
extract expression parser and template compiler into own packages
etc...
📍 Iteration plan
The main goal of completing everything that would cause uncomfortable changes in RC
The aim of the development in Q1 is to resolve all beta & RC related issue, by either implementing or closing/moving the target date to another time, and go for an RC release at the end of the Q1 2024, or latest early Q2 2024.
Issue list:
A roadmap and an iteration plan will be provided & updated below for better clarity on the focus of the development.
🗺️ Roadmap
Main work to be completed during this time will be the final features that may require some "buffer" versions to stabilize the behavior, the bellow list comprises the significant ones (but not all):
📍 Iteration plan
✔️ Statuses
this
expression<au-compose>
host behavior<au-compose>
supports string as component name🏁 Next steps
The text was updated successfully, but these errors were encountered: