-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chart: Append/Replace Data Option #358
Comments
First discussed here: https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/237?u=joepavitt |
I think it may be more important that it is available as a msg property than as a config item. It is common to preload the chart with historical data and then add further data in real time. |
This has now been requested by multiple people, bumping up the priority |
My thoughts as a very new Node-red dashboard user
I really appreciate what you guys are doing |
Very good point - we could/should also have this feature added to table for consistency.
Two reasons:
It's not too much, but definitely a laziness on my part. Linking to the online docs is a great idea though, but I do need to get the Editor help text updated, as Node-RED is regularly used in constrained environments where access to the general Internet isn't guaranteed. |
Description
By default, we assume that any newly received data into
ui-chart
should be appended to the existing data on the chart, however, in the case of showing API data for example, we may actually just want to replace the entire dataset with the newly received data.Whilst this can be achieved by sending a
[]
msg to the chart to clear data, a lower-code approach would be to provide a configuration option on the chart itself which provided the option to "Append" or "Replace", maybe even being able to define this as aTypedInput
, so that we can control it on a msg by msg basis.Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
The text was updated successfully, but these errors were encountered: