Make shorthands a little magic about bss HOT 13 CLOSED

Personally I'm happy with things as they are now...using helpers is pretty easy 🙂

from bss.

Wouldn't there be a problem when you want border: 0 and do b(0)?

from bss.

Wouldn't you write b none?

from bss.

Hmm sadly not I see 😄 https://stackoverflow.com/questions/2922909/should-i-use-border-none-or-border-0

Yeah, so that might be a pretty annoying gotcha..

from bss.

👍

“Premature optimization is the root of all evil”
- Donald Knuth.

Maybe no magic rather than little magic 😄

If a project use bss with shortcuts all over, then it's very hard to be transformed, and if later refactored by another person, and what if he/she don't know bss at all?

Shortcut is cool! But, less magic is better.

Sorry for the noise 😄 it's maybe not related to the issue at all.

from bss.

You could of course implement a number of bss specific shorthands, like bo for border, bor for border-radius, and br/bl/bb/bt for the specific borders. Atm I use helpers for those, as well as f.e.:
abs: b.position('absolute'), which is still shorter than p absolute 😉

from bss.

@futurist Yeah, that's also my main pain point about it.. It's the same kind of footgun that helpers can invite.

Speaking of helpers, I guess this solution could easily be written as a helper too though

b.helper({
  p: (v, ...rest) => /[0-9]/.test(v)
    ? b.padding(v, ...rest)
    : b.position(v)

from bss.

@osban Hehe.. br works for border-radius ;)

I don't like the inconsistency of having bo et al.. It's kind of an unpredictable rule..

from bss.

@porsager I know, but I don't like the inconsistency of
bt = border-top
bl = border-left
br = border-radius <-- should be border-right
bb = ? <-- should be border-bottom
😉

from bss.

Hehe.. that's why they're not directly mapped in bss :P I think I should probably be more strict about the shorthands instead of automapping ones which aren't in https://github.com/porsager/bss/blob/master/lib/popular.js

It suffers a bit from my personal usage in that I almost never use borders, so not having a shorthand for borders was never an issue for me..

from bss.

Cool. Thanks for the feedback everyone 😉

I'd like to add some better descriptions for helpers in the docs and some conventions for building helper libraries as well..

from bss.

I would also keep it as is. Maybe optionally with a config flag to choose from a predefined list of flavors e. g. (1) Tachyons, (2) Basscss, (3) maybe SuitCss, are there others? No magic necessary.

from bss.

@smuemd Yeah, those could simply be extra libraries used like

import tachyons from 'bss-tachyons'
b.helper(tachyons)

from bss.