Consider state middleware injection as extensibility mechanism #692
Labels
[Feature] Extensibility
The ability to extend blocks or the editing experience
Framework
Issues related to broader framework topics, especially as it relates to javascript
[Type] Question
Questions about the design or development of the editor.
Related: #594
In #594, when a post draft finishes saving, we adjust the current browser URL to reflect the new post ID. While this is necessary in the context of the dedicated editor screen, this reduces the portability of the editor as these URL changes are not applicable outside this context. If we'd want to allow initializing an editor on other screens (e.g. front-end, Customizer), we might need to explore options for injecting context-specific middlewares. This could serve as a generic extensibility pattern for any side effects of state changes.
For the post save navigation example, this could look something like:
See also:
middleware
)The text was updated successfully, but these errors were encountered: