Make a separate dev build to provide useful warning messages about aphrodite HOT 5 CLOSED

Could make an eslint plugin. That'd be pretty awesome

from aphrodite.

@xymostech you're probably right... I guess I miss the validation my editor usually gives me in .css/.less files. Maybe someone will build a separate thing for validating aphrodite styles at compile/lint time.

from aphrodite.

It would also be nice to validate values , e.g. display: 'inline-blick' should cause a warning in dev. Obviously some props are easier to validate than others.

from aphrodite.

It would also be nice to validate values , e.g. display: 'inline-blick'

With the goal of not including a CSS parser in aphrodite, I'd be against this sort of validation. We'd also start yelling at people about new CSS standards (who is to say that "inline-blick" won't be the new hotness in the future?!)

from aphrodite.

While I think there is probably room for better error messages in dev, this issue isn't very actionable so I'm going to close it. If you disagree, please open a new issue with a more actionable proposal!

from aphrodite.