Hi!
First, let me thank you for having made this wonderful tool! It is amazing what you as a single programmer have achieved! Since I am using devcards, I found that the quality of my components
goes up dramatically. This is because devcards is the equivalent to unit testing for UI design. Thanks!!
I have the following question: I am using devcards with {:inspect-data true}. This is nice as I
can see the state that is passed to the component, and I can see what it does in edge cases.
Now I do see that while it is possible to PASS MULTIPLE PARAMETER to the devcard component, it is only displaying the first parameter. Is there a reason for this? Do you think developers should
by default only pass one parameter to a component? Or in other words if multiple parameters
are needed, then they have to be passed as a map.
It would be nice to visualize multiple parameters in devcards, so I am wondering what options you think are available. At least my own app design uses multiple parameters in many components.
Hi! First, let me thank you for having made this wonderful tool! It is amazing what you as a single programmer have achieved! Since I am using devcards, I found that the quality of my components goes up dramatically. This is because devcards is the equivalent to unit testing for UI design. Thanks!!
I have the following question: I am using devcards with {:inspect-data true}. This is nice as I can see the state that is passed to the component, and I can see what it does in edge cases.
Now I do see that while it is possible to PASS MULTIPLE PARAMETER to the devcard component, it is only displaying the first parameter. Is there a reason for this? Do you think developers should by default only pass one parameter to a component? Or in other words if multiple parameters are needed, then they have to be passed as a map.
It would be nice to visualize multiple parameters in devcards, so I am wondering what options you think are available. At least my own app design uses multiple parameters in many components.
Thanks!