Skip to content

Turn inline editing decorators into general extensions API#2391

Merged
tf merged 2 commits intocodevise:masterfrom
tf:extensible
Apr 7, 2026
Merged

Turn inline editing decorators into general extensions API#2391
tf merged 2 commits intocodevise:masterfrom
tf:extensible

Conversation

@tf
Copy link
Copy Markdown
Member

@tf tf commented Apr 7, 2026

REDMINE-21261

@tf tf added this to the v17.2 milestone Apr 7, 2026
tf added 2 commits April 7, 2026 10:38
Components no longer decide whether they are decorated or
replaced — they just declare themselves as extensible via
`extensible('Name', Component)`. The extension provider
(e.g. inline editing) decides the extension type by placing
components into either `decorators` or `alternatives` when
calling `provideExtensions`.

REDMINE-21261
Allow extensions to be provided after initial render (e.g. via
dynamic import after hydration). A single ExtensionsProvider at
the root subscribes to extension changes and propagates updates
via context, avoiding per-component subscriptions.

REDMINE-21261
@tf tf merged commit c382b19 into codevise:master Apr 7, 2026
18 checks passed
@tf tf deleted the extensible branch April 7, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant