Part of #620. Configurations are not linked to a project: every configuration in the store belongs implicitly to the single project. The multi-project payload in #620 needs (project.id, configuration.id) as the address of each configuration.
- Add
projectId to ConfigInterface, set from the active project when a configuration is created
- Make the config store queries take a project (
getConfigsForProject, removeAllForProject); use them in the UI and in buildSequencePayload
- Save the active project when it is created, not only when it changes
- After the stores load from local storage, attach any configuration without a valid
projectId to the active project, so existing data keeps working
No multi-project UI yet.
Acceptance: existing local storage loads without losing any configuration; client tests and golden tests unchanged.
Specification
docs/selection-keys.md, sections "Stores" and "Payload".
Part of #620. Configurations are not linked to a project: every configuration in the store belongs implicitly to the single project. The multi-project payload in #620 needs
(project.id, configuration.id)as the address of each configuration.projectIdtoConfigInterface, set from the active project when a configuration is createdgetConfigsForProject,removeAllForProject); use them in the UI and inbuildSequencePayloadprojectIdto the active project, so existing data keeps workingNo multi-project UI yet.
Acceptance: existing local storage loads without losing any configuration; client tests and golden tests unchanged.
Specification
docs/selection-keys.md, sections "Stores" and "Payload".