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
{{ message }}
This repository has been archived by the owner on Jun 9, 2019. It is now read-only.
I'm trying to understand the need of this tool. Is this a some kind of ui component testing tool?
I'm also not understanding it's use, if I can't build complex play components with state and also those without states but they require props. I think I also can't reuse my data method to pass data to component by hitting a api request or any lifecycle hook as I mostly prepare my data there or do my required changes .
My particular usecase is like to have a framework where my designers who write html and css can build the components themselves and see and affirm how the component's vary based on simplest changes in data point's or mock data such as something like below.
Like I have MyButton.vue component which can be directly used in any app by just including it and it has contents like below, but I also want to see every possible case where myButton could have a changed way of rendering itself based on different conditions such it's place in material-design based template or just bootstrap based. Can such a thing in vue-play could be achieved by just speifying the template, css and then for each scenario I can hardCode the required props,data,methods
and what I'm expecting play will do is like, I'll have a page level, component's config file containting all the possible components possible on that particular page. And then for each component I can hardcode my scenarios or cases with variable inputs such as following
Hi
I'm trying to understand the need of this tool. Is this a some kind of ui component testing tool?
I'm also not understanding it's use, if I can't build complex play components with state and also those without states but they require props. I think I also can't reuse my data method to pass data to component by hitting a api request or any lifecycle hook as I mostly prepare my data there or do my required changes .
My particular usecase is like to have a framework where my designers who write html and css can build the components themselves and see and affirm how the component's vary based on simplest changes in data point's or mock data such as something like below.
Like I have MyButton.vue component which can be directly used in any app by just including it and it has contents like below, but I also want to see every possible case where myButton could have a changed way of rendering itself based on different conditions such it's place in material-design based template or just bootstrap based. Can such a thing in vue-play could be achieved by just speifying the template, css and then for each scenario I can hardCode the required props,data,methods
and what I'm expecting play will do is like, I'll have a page level, component's config file containting all the possible components possible on that particular page. And then for each component I can hardcode my scenarios or cases with variable inputs such as following
<myButton prop1="onClickAmbulance"><myButton>
<myButton prop1="onClickPolice" prop2="useClickSWAT"></myButton>
<someOtherComponent prop3="myButtonAsTrigger"></someOtheComponent>
The text was updated successfully, but these errors were encountered: