mistercrunch commented on issue #33448:
URL: https://github.com/apache/superset/issues/33448#issuecomment-3199295196
Yeah I think the key would be around hiding or disabling functionality in
certain modes, say you prevent some panels from rendering (dataset panel,
disable DnD, controls or controls section, results/sample panel,
properties/actions).
At a high level if there was a public API component for `<Explore />`, you
could have props like `showDatasetPanel={false}`, `exposedControls={}` or
`hiddenControls={}` or `showResultsPane={false}`. Alternate views / layouts
with things like `metadataPanelPosition="right"`.
Clearly would be nice to embed a React component that's a subset of Explore
in some other app or in a chatbot session through an MCP call. Save/recall
becomes a bit of a puzzle, and the whole controlled/uncontrolled component
spectrum can be hard to reason about.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
