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.

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

Warnings for nested properties #352

Closed
claudiopro opened this issue Oct 26, 2015 · 5 comments · Fixed by #701
Closed

Warnings for nested properties #352

claudiopro opened this issue Oct 26, 2015 · 5 comments · Fixed by #701
Assignees
Labels
Milestone

Comments

@claudiopro
Copy link

This example of nested properties from the docs:

.funky {
  font: {
    family: fantasy;
    size: 30em;
    weight: bold;
  }
}

Produces the following warnings:

2:8  warning  Whitespace required before {                         space-before-brace
2:9  warning  Trailing semicolons required                         trailing-semicolon
3:5  warning  Property `family` appears to be spelled incorrectly  no-misspelled-properties
5:5  warning  Property `weight` appears to be spelled incorrectly  no-misspelled-properties
@claudiopro
Copy link
Author

$ sass-lint -V
1.3.1

@DanPurdy DanPurdy added the bug label Oct 26, 2015
@DanPurdy
Copy link
Member

Confirmed as issue in 1.3.1, we'll look into it, thanks @claudiopro

@claudiopro
Copy link
Author

@DanPurdy cheers! Let me know how/if I can help

@DanPurdy
Copy link
Member

@claudiopro 2 of your 3 issues are sorted in 1.3.2 which we just released, the only one still affected here is no-misspelled-properties which I was looking into yesterday, still to decide on a good solution for handling nested properties with it but I think it'll either be fixed in 1.3.3 or 1.4.0 which shouldn't be more than a few days / week away.

@claudiopro
Copy link
Author

That's awesome, thanks for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants