-
Notifications
You must be signed in to change notification settings - Fork 426
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
feat: save semantic viewer charts and add in the dashboards #11485
Conversation
✅ Deploy Preview for peaceful-bassi-cbf284 canceled.
|
0803e2d
to
afd2937
Compare
organizationId: string; | ||
chartKind: ChartKind; | ||
semanticLayerQuery: SemanticLayerQuery; | ||
barChart?: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this does not have table config. do we also need to keep all configuration blobs as the analytics event or the active one @TuringLovesDeathMetal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean, sorry irakli?
I'd expect each saved chart created new saved chart version to have the table config if we're sharing an analytics event for each save chart.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TuringLovesDeathMetalsSorry for providing less than a zero context 😂
I noticed that with SQL Runner, when you save a chart, we fire an analytics event. The analytics event includes all of the configurations for all charts, not just the active chart that's being used. Additionally, we are not including the table visualization configuration at all. I copied this "blindly" from SQL Runner but left a comment not to forget to update both places if needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The analytics event includes all of the configurations for all charts, not just the active chart that's being used.
wut - that sounds wild 😂
Ya, can we just include the active chart configuration. Also, if there's a table visualization, then include it's configuration
user.ability.cannot( | ||
'manage', | ||
// TODO: add it's own ability | ||
subject('CustomSql', { organizationUuid, projectUuid }), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add ability
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can be done as a separate ticket
fields, | ||
query: data.chart.semanticLayerQuery, | ||
rows: chartData.results, | ||
columns: [], // TODO: sqlRunnerChartData.columns, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forgot column conversion here
@@ -107,20 101,21 @@ const Sidebar: FC<React.PropsWithChildren<Props>> = ({ | |||
> | |||
{(style) => ( | |||
<> | |||
<Card |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
card is too opinionated to be a sidebar component
28890f8
to
6a28b4c
Compare
2010f22
to
5145cb4
Compare
5145cb4
to
890e20a
Compare
# [0.1256.0](0.1255.6...0.1256.0) (2024-09-16) ### Features * save semantic viewer charts and add in the dashboards ([#11485](#11485)) ([e02ff01](e02ff01))
🎉 This PR is included in version 0.1256.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Closes: #11366
Closes: #11368
Description:
Reviewer actions