Currently the editor web component has limited state and functionality. To enable the retrieval, remixing and saving of code the web component needs access to more initial state and redux functionality of the standalone editor.
NB To be refined further to determine core functionality but consider if it's easier to utilise the same setup for the web component as the standalone editor.
Refinement
As far as I'm aware, all of this functionality is theoretically available in the web component, just not enabled, for example, because those parts of the UI are not visible, or toggled off with the forWebComponent flag
We are currently using the same store for the web component as for the standalone editor (see web-component.js and WebComponent.md)
The version of the web component enabling the loading/saving/remixing of projects will encompass even more of the functionality of the standalone editor, so we should continue with our existing setup of using the same store and reducers as we are for the standalone editor.
To enable loading, saving, remixing etc from the web component, we should productionise the spike linked below
This ticket depends on the implementation of the authentication of the web component via the host application
create-issue-branch[bot]
commented
10 months ago
Currently the editor web component has limited state and functionality. To enable the retrieval, remixing and saving of code the web component needs access to more initial state and redux functionality of the standalone editor.
NB To be refined further to determine core functionality but consider if it's easier to utilise the same setup for the web component as the standalone editor.
Refinement
forWebComponentflagstorefor the web component as for the standalone editor (seeweb-component.jsandWebComponent.md)Existing spike PR
https://github.com/RaspberryPiFoundation/editor-ui/pull/676