feat(tag): visualize history of multiple tags #60
Conversation
update descriptions minor changes
TigranVardanyan
changed the title
add workspace column for current query
There was a problem hiding this comment.
I tested this out locally and the data isn't looking like how I would expect. Even when the timestamps match up, the columns alternate missing values, which seems to create gaps in the chart.
It gets weirder when your tags aren't updating at the same frequency.
There's not any way to guarantee that the tag history returned by the query will have uniform timestamps, so I think what we should do is return each tag in a separate data frame/series (the second example in these docs).
This is the first time we've needed to do this in a plugin, so we'll need to make the runQuery method support returning a list of data frames: DataFrameDTO[]
One advantage of this approach is that we can continue to have the Properties toggle for the history query instead of hiding it.
|
@markacamps @TigranVardanyan - Carson left a comment yesterday related to the return type of the |
We won't need to do this if we're only returning one data frame, as was the outcome of the other conversation |
|
@mure is this clear to merge? |
Done |
## [3.13.0](v3.12.1...v3.13.0) (2024-09-11) ### Features * **tag:** visualize history of multiple tags ([#60](#60)) ([5826522](5826522))
|
🎉 This PR is included in version 3.13.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Pull Request
🤨 Rationale
The "history" query type currently visualizes data only for the first matched tag. Need to visualize data from all matched tags.
👩💻 Implementation
Implemented functions to retrieve tag history in chunks and merge responses into a single dataframe. Since it is impossible to have properties of multiple tags in one dataframe with those historical values, "Properties" option in now available only for query type "Current".
🧪 Testing
Added a test to check if the history of multiple tags is processed correctly. Added a test to ensure the properties switch button is hidden when the query type is "History".
✅ Checklist