Conversation
Contributor
|
Is there information publicly available on what this is about? The Flowfuse/engineering issue is not accessible. |
n-lark
added this pull request to stack #2231
September 15, 2026 20:05
Contributor
Author
|
Hey @colinl I'll get the issues moved to this repo before I move this out of draft. Will report back. |
Contributor
Author
n-lark
marked this pull request as ready for review
September 17, 2026 20:26
Contributor
|
So I see, thanks. This will keep you busy for a while :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Important
This is part of a multi stage epic and should NOT be merged to main as is.
Plumbing only: the store exists in global context but nothing reads from it yet, so dashboards behave exactly as before.
The store
nodes/store/reactive.jsis a proxy-backed store where writing a value is the change event, so there is no separate "store it, then emit it" step. Each key holds an entry with the value plus room for quality, timestamp and history. Reads return the value by default, and a$prefix returns the full record:Nested objects and arrays are watched too, so a deep change still fires the event. The backing object has a null prototype with prototype-pollution guards, clones on write so a flow cannot corrupt stored state, and flattens to plain
{ key: value }for serialisation.Injection
ui-baseinjects the store into global context atglobal.dashboardStoreon startup. It is idempotent across multiple base nodes and redeploys, so the same store is reused, and it rehydrates existing data after a restart.Related Issue(s)
Closes #2236
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel