You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the Composum Dashboard context aware configuration view we could have a view in the Browser that shows context aware configurations. At minimum a read only view like in the dashboard, at best an editor that does what the wcm.io config editor does.
The behaviour needs some thought, as the configurations are referred at the resource but are actually somewhere else - perhaps we show links to the actual configuration resource at the /content/ resource and at the configuration resource we show an actual editor. That'd diverge from the wcm.io editor, though, but might make it an alternative that might make it clearly preferable for some users.
Interesting point: the configurations could contain secret keys like the OpenAI API key in Composum AI. But that'll only displayed if the user would have access to the configurations using the browser, anyway.
The text was updated successfully, but these errors were encountered:
Similar to the Composum Dashboard context aware configuration view we could have a view in the Browser that shows context aware configurations. At minimum a read only view like in the dashboard, at best an editor that does what the wcm.io config editor does.
The behaviour needs some thought, as the configurations are referred at the resource but are actually somewhere else - perhaps we show links to the actual configuration resource at the /content/ resource and at the configuration resource we show an actual editor. That'd diverge from the wcm.io editor, though, but might make it an alternative that might make it clearly preferable for some users.
Interesting point: the configurations could contain secret keys like the OpenAI API key in Composum AI. But that'll only displayed if the user would have access to the configurations using the browser, anyway.
The text was updated successfully, but these errors were encountered: