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

[Indented syntax improvements] Specs #2041

Open
wants to merge 54 commits into
base: main
Choose a base branch
from

Conversation

jamesnw
Copy link
Contributor

@jamesnw jamesnw commented Dec 16, 2024

Blocked until proposal is accepted.

[skip dart-sass]
[skip sass-embedded]

@jamesnw jamesnw requested a review from nex3 January 11, 2025 02:10
Copy link
Contributor

@nex3 nex3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other expressions that should probably have whitespace tests include parentheses and function calls.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since these are testing newlines, not just any whitespace, something in the test names should reflect that.

Comment on lines +64 to +65
/* foo
* bar */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this change correct, or was there a CR in the original that doesn't render properly on GitHub?


<===>
================================================================================
<===> loud/multi_line/sass/input.sass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Error tests should generally be the last thing in an HRX file.


<===>
================================================================================
<===> multiline-list/paren/sass/input.sass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


<===>
================================================================================
<===> multiline-list/paren/sass/input.sass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since there's no reason to test multiline lists for SCSS at all, I'd put them under an indented syntax directory instead of vice versa.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you need to test whitespace separately for each separate operator type. All binary operators are parsed essentially the same.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you need to test this separately for every place an interpolation can appear.

@@ -48,6 +48,27 @@ b {
c: d;
}

<===>
================================================================================
<===> multiline-no-comma/input.sass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably go under whitespace/.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about cases like a\n, b and a +\nb?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't these redundant with the tests you have in individual statement directories?

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

Successfully merging this pull request may close these issues.

2 participants