JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Relying on object property order for a styling API. Good or bad? eg. styles({ backgroundBlue: true, backgroundRed: true, }); In this case the background would be `red` as it appears last. Relying on property order feels gross but can't think of a better API?
I'm hiding some higher abstraction we have. It's more like: styles({default: true, active: isActive}); Where `active` and `default` are a bunch of CSS rules.
It is! Object order has been guaranteed in JS since ES2015. Just feels like an odd API.
So I guess that leaves: are your keys actual classnames or inline-styles to be applied? Because if they're classnames on the same element, the order in the classname list is irrelevant, but if they're styles the outcome could be different.
I think this pattern is fine. If there are things that directly conflict like <Comp red blue /> for "background: blue" and "background: red", I would throw an error if both are applied, but it's more about how the implementation is meant to be used.
if default you always need it, only depend on isActive. IMO then instead of object, you'd need properly inherit from CSS rules, where active css rule rewrite some default rule.
maybe it'd be clear if it was something like `styles({default: true, overrideStyles: {active: isActive}})`
This gets tricky when there're more than two styles.
IMHO, this specific case is idiomatic enough that people will assume that order DOES matter even when they would otherwise argue to their death that it doesn't.
People are funny like that 
So I'm changing my vote to YES :D
Thanks for the specific example. Details matter.
This example looks and feels a lot better.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
