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
So im not sure if this has been brought up before. I searched the issues and didnt see anything. Im looking for a way to handle some added functionality in component demos. Right now we have the View Code option and the option to route to isolated demo.
Is there a way to add some additional info into the config that would allow us to add something under the demo along with the default actions? See below:
What im trying to accomplish is to allow for us to create an elegant way to render large components as full screen( without routing, think of a full screen modal ). I think it would be really clean to be able to add to that demo footer instead of jumbling up the demo body.
Our use case is strictly for full screen functionality but a possible config setting coupled with some sort of parameters in the declaration could be super useful:
So im not sure if this has been brought up before. I searched the issues and didnt see anything. Im looking for a way to handle some added functionality in component demos. Right now we have the View Code option and the option to route to isolated demo.
Is there a way to add some additional info into the config that would allow us to add something under the demo along with the default actions? See below:
What im trying to accomplish is to allow for us to create an elegant way to render large components as full screen( without routing, think of a full screen modal ). I think it would be really clean to be able to add to that demo footer instead of jumbling up the demo body.
Our use case is strictly for full screen functionality but a possible config setting coupled with some sort of parameters in the declaration could be super useful:
```js {file: '../../../someDemo.js, addedButton: {label: '...svg', onClick: ()=>someFunction()} ```
The text was updated successfully, but these errors were encountered: