mistercrunch commented on issue #32854:
URL: https://github.com/apache/superset/issues/32854#issuecomment-2791220088
NOTE: Directionally, I think the folks that were part of the conversation
want to build minimal hooks for people to build-upon, and leave functionality
to the extension implementation - note that extensions can still be open
sourced and shared within the community, but directionally trying to contain
the core project's surface. Question becomes more about offering the right
interfaces for people building extensions.
Out of all of this I like the idea of `templated_fields` in core Superset
models to allow for dynamic / extensible model properties. Some of what it
enables - beyond i18n:
- Rich/dynamic descriptions with AI subsystem where say a chart description
could be `{{ llm_interface_describe_chart(chart_object) }}`
- reference object properties in titles: `My dashboard (as of {{
obj.last_modified }})`
- i18n composition: `{{ ai18n("Dashboard") }} - {{ ai18n("by month") }}`,
where smaller - more atomic strings can be instrumented for translations
- showing chart defining filters in titles: `Population by country for {{
main_time_filter.humanize() }}`
- dynamically reference metric or dimension names in chart titles `{{
main_metric.label }} by {{ main_dimension.label }}`
- surfacing things like when the dashboard was rendered in its title
`Incident report as of {{ now().isoformat() }}` - say for alerts and reports
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
