-
Notifications
You must be signed in to change notification settings - Fork 234
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
RFC Blogpost for indented syntax #1260
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for sass-lang ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
```sass | ||
@each $item in ¹ | ||
1 2 3 | ||
.item-#{ ² | ||
$item | ||
} | ||
content: $item * ³ | ||
10 | ||
``` | ||
|
||
1. A statement can't end after the word "in" in an `@each` statement. | ||
2. A statement can't end inside the curly braces in an interpolation. | ||
3. A statement can't end after a multiplication operator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these references might be easier to parse if they used line numbers instead of superscript. Or I'm not sure if there's a better way to make it clear that they're not part of the code example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
linebreak is treated as whitespace. This means that if the parser can't tell | ||
whether or not a linebreak is intended to end a statement, it will end the | ||
statement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be helpful to also include a code example showing the "parser can't tell" path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in 2002663
@nex3 This is ready for review. It currently has today's date (11-27) but given the holiday, I could update that to next week if you'd prefer. |
No description provided.