corset
corset copied to clipboard
Declarative data bindings, bring your own backend.
Assuming the data-corset-prop-* attrs are there individually just for an internal query selector and not a deeper need, would you consider changing it to be all contained in one `data-corset-props`...
Reduced example: https://codepen.io/propjockey/pen/poLppJX/2c1726852bc96c8bf7703c95486a97c5?editors=1010 The each-template prop uses a var that is referencing `--bad-match` which doesn't exist, but is substituted with the value on var called --bad-match2. If `--bad-match2` ends with...
Corset v1 and v2 in the following Corset sheet code, `var(--onSelected, false)` is resolving as false: ```css [role="group"] { --onSelected: ${x => console.log(x)}; event: pointerdown bind( ${this.someEvent}, var(--onSelected, false) );...
Similar to `attr-toggle`, removes the attribute when the value is false. ```css #app { data-value: theme dark; data-toggle: theme true; } #app:not(.dark-mode) { data-toggle: theme false; } ```
Using in an esbuild project is more difficult than I expected because of the use of a wasm module. Need to investigate how to do this.
Probably integer and float types but need to research what CSS's are.