Skip to content

fix: don't consider used rules with atrules in the block #13410

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

Merged
merged 4 commits into from
Sep 27, 2024

Conversation

paoloricciuti
Copy link
Member

Svelte 5 rewrite

Closes #13390

I spend quite a bit of time to try to fix this just to realise that there's no reason a nested AtRule should mark the wrapping rule as used.

.foo {
  display: grid;
  @media (orientation: landscape) {
    grid-auto-flow: column;
  }
}

this is equivalent to

.foo {
  display: grid;
}

@media (orientation: landscape) {
  .foo {
    grid-auto-flow: column;
  }
}

but if foo is unused it will still be unused inside the media query.

Please note that the Svelte codebase is currently being rewritten for Svelte 5. Changes should target Svelte 5, which lives on the default branch (main).

If your PR concerns Svelte 4 (including updates to svelte.dev.docs), please ensure the base branch is svelte-4 and not main.

Before submitting the PR, please make sure you do the following

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests and linting

  • Run the tests with pnpm test and lint the project with pnpm lint

Copy link

changeset-bot bot commented Sep 26, 2024

🦋 Changeset detected

Latest commit: 4776e71

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@dummdidumm
Copy link
Member

This will wrongfully mark things within media queries as unused - will fix this. Otherwise this PR makes sense.

@paoloricciuti
Copy link
Member Author

This will wrongfully mark things within media queries as unused - will fix this. Otherwise this PR makes sense.

Isn't this just looking at the children of the rules?

@paoloricciuti
Copy link
Member Author

Like if i only have a media query it still mark it as used.

And if i have something like this

.foo {
  display: grid;
  @media (min-width: 60px) {
    grid-auto-flow: column;
    
    .bar{
      color: red;
    }
  }
}

if .foo is unused .bar will be unused too because it still needs to be inside foo

@dummdidumm
Copy link
Member

Yeah I confused myself there ... now I'm thinking why this child loop is even there. If every selector is unused, how would it even be possible for a child to be used?

@paoloricciuti
Copy link
Member Author

thinking

Yeah i think you are right...it's checking if some rule is used but if there's no foo each foo > * can't be used anyway.

@@ -333,7 +333,7 @@ function is_empty(rule) {
}

if (child.type === 'Atrule') {
return false; // TODO
if (child.block === null || child.block.children.length > 0) return false;
Copy link
Member Author

Choose a reason for hiding this comment

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

Should this be child.block !== null? How does a media query with a null block looks like?

Copy link
Member

@dummdidumm dummdidumm Sep 27, 2024

Choose a reason for hiding this comment

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

an AtRule can also be something like @import ... which has no child block, which means something is happening within the rule

Copy link
Member

@dummdidumm dummdidumm left a comment

Choose a reason for hiding this comment

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

The simplification has to be correct. It's shown by the fact that this bug was produced previously: There's pruning logic in a different place where all unused selectors are commented out. If all selectors are unused, the whole prelude is commented out, resulting in invalid syntax. This is a case that can't happen.

@dummdidumm dummdidumm merged commit 30c438c into main Sep 27, 2024
8 of 9 checks passed
@dummdidumm dummdidumm deleted the fix-invalid-css-atrules branch September 27, 2024 10:45
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.

Nested atrule in unused selector results in broken CSS output
2 participants