This message was deleted.
# secoda-feature-requests
w
This message was deleted.
p
The resource would be aware of
this
, e.g. the
this.name
this.schema
this.database
this.source
this.description
this.tags
this.columns
and my Template could be populated using those context-aware variables
One thing that I’d like to do is dynamically embed resource-specific content - that might be a form, a metabase embed, or a query that is paramaterized by the
this. vars
l
Hey! I think we missed this. Sorry about that @polite-microphone-78573. I think that would be pretty awesome. Especially with resources like “queries” or “charts”. Are you finding that there are a lot of cases in the docs that this would help?
p
definitely. i'm monitoring tests for dbt with the built-in UI from re_data. it would be awesome to dynamically link each table to its relevant page (embeds would be even better but haven't worked that out yet). The URL structure of that framework would be easy to point to. see https://docs.getre.io/ui-latest/#/graph?model=postgres.toy_shop.orders&tab=test
1
e
Thanks for the additional details @polite-microphone-78573. cc @lively-helicopter-98030 the re_data looks like it has some interesting features that would be relevant to our lineage graph
🙌 3
l
This is really cool @polite-microphone-78573
😎 1