Hey everyone, another round of feedback needed for future improvements to classes and states.
What are your biggest wants/needs/issues about our current classes & states system?
the custom css properties should not be changed exclusively like any other property but it should be addictive between multiple states/classes and let browser css rules apply the resulting styles.
Combo classes would be great as Mariano said. Less boilerplate would also be nice, so the classes would actually work.
Could you elaborate on what you consider boilerplate?
This might be a bit off-topic, but as someone that had their first ‘major’ web dev experience using WeWeb, it’s very difficult for me to know when I should be using classes vs components/formulas.
I’ve found I’m using components and formulas for just about everything but have no clue when I should be using classes, or why I should ever use classes.
Would love to see documentation or videos showcasing when it’s best to use formulas, vs components vs classes!
1 Like
Hopefully not too late to add a request related to this.
Some kind of state exposure for an element’s default and custom states would be amazing.
For example, if I have the default ‘hover’ state and a custom ‘active’ state set up on an element, and I want to have a different hover state depending on if the element is active or not, currently I either have to manually create a hover state using the mouse enter/leave triggers or set up conditional binding within the default hover state.
It would make life a lot easier if I had access to the element’s possible states, as in the example given I could just create a state for when ‘hover’ and ‘active’ are true and another for when ‘hover’ is true and ‘active’ is false.
1 Like
@luka this PLEASE
Maybe it’s a minor UX issue or applies only to me but it’s a bit hard to understand the hierarchy in which different states are applied on an element if there are multiple custom states that meet a specific condition.
1 Like