hhmx.de

· Föderation EN Mi 26.06.2024 00:14:26

@simevidas This seems to be only functions? And only returning single string values?

This isn't wnat I expect from "mixins".

I expect this from mixins:

```
@mixin bob {
prop: val;
otherProp: other val;
}

.thing {
@mixin bob;
...
}
```

e.g.,

Define heading styles, and include them where needed.

WITHOUT:

- code repetition
- a massive selector list divorced from context
- relying on naked heading levels
- relying on utility classes

Functions I never use in SCSS. ^ that I do. A lot.

Föderation EN Mi 26.06.2024 00:29:18

@MattWilcox @simevidas To clarify:

- This is only the first commit to an early Editor's Draft spec that will eventually include both mixins and functions.

- The `type(<string>)` bit means that the type function *accepts a string argument* which defines the return type. Not that the return type can only be single string values.

Föderation EN Mi 26.06.2024 00:32:58

@mia @MattWilcox@mastodon.social @simevidas Thank you! Thats the vital context I’d missed and didn’t grok from the link :)

Föderation EN Mi 26.06.2024 12:19:59

@mattwilcox@mstdn.social @mia @MattWilcox@mastodon.social @simevidas Initial commit, not final spec (not even first public working draft).

Also, from a load-balancing and burnout prevention angle, good to see another NJT&F spec (Not Just Tab & Fantasai).

Föderation EN Mi 26.06.2024 12:58:35

@svgeesus Yeah, good to see. Once upon a time I tried getting involved with this sort of stuff, but I was not cut out for it. I was in the HTML-WG and Responsive Images Community Group, and that's as far as I could take things before my irritation with process got the better of me. My respect to those who do the work we all benefit from. @mia @MattWilcox@mastodon.social @simevidas