Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Strict mode #139

Open
eevee opened this issue May 3, 2013 · 0 comments
Open

Strict mode #139

eevee opened this issue May 3, 2013 · 0 comments
Labels
back compat Ruby parity

Comments

@eevee
Copy link
Collaborator

eevee commented May 3, 2013

I call it strict mode, but it should really be the default, and should only be turned off for backwards compatibility.

Some things that should be errors:

  • Invalid syntax
  • @include with an unrecognized mixin name
  • Unrecognized variable names

Note that some particularly egregious constructs like IE's expression still need to make it through unscathed.

Some things that are hard to make strict, but may be opt-in warnings or linters:

  • Unrecognized function name (i.e. not in any known CSS either)
  • Relying on -/_ equivalence
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
back compat Ruby parity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eevee