Feature/dash cohort#20
Conversation
| @@ -0,0 +1,126 @@ | |||
|
|
|||
| from dotwiz import DotWiz | |||
| return filters | ||
|
|
||
|
|
||
| @callback( |
There was a problem hiding this comment.
what is this @callback( ) syntax supposed to do?
| # data = query_service.query("{ program(first:0) { id name projects { id code } } }") | ||
| # logger.error(data) | ||
|
|
||
| simplified_authz = {k: ','.join([m['method'] for m in v]) for k, v in get_authz().items()} |
There was a problem hiding this comment.
kindof interesting that authorization information is put into a dataframe. Does this hold more than just auth information
|
So what I can gather/summarize from this PR is that you're harvesting information from the data dictionary through queries and then displaying that information via histograms/other data objects that are being inserted into the DOM with the queried information. Is this vaguely correct? |
| 'index': f"{entity}-{k}", | ||
| 'type': 'query-parameter' | ||
| }, | ||
| options=[ |
There was a problem hiding this comment.
is this a style structure?
| return checklists, dfs, names | ||
|
|
||
|
|
||
| def histogram_sliders(histograms): |
There was a problem hiding this comment.
what are histogram sliders?
| Input({'type': 'query-parameter', 'index': ALL}, 'value'), | ||
| Input({'type': 'query-parameter', 'index': ALL}, 'id') | ||
| ) | ||
| def update_counters(values, ids): |
There was a problem hiding this comment.
so I guess the callback functionality attaches to some sort of external button since it is not directly called anywhere within this commit?
| dbc.Tab(observation_accordian, label="Observations"), | ||
| ] | ||
| ), | ||
| dash_table.DataTable(id='results'), |
There was a problem hiding this comment.
What is this giant return list doing? It looks like Structural HTML, but I'm not sure what purpose it serves.
instructions for local windmill setup
fixed the formatting
Change to local data-portal build for Windmill
3 participants
This PR creates a dash based cohort builder