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

[v3 checks] Update instances of class:list #4278

Closed
sarah11918 opened this issue Aug 19, 2023 · 1 comment · Fixed by #4322
Closed

[v3 checks] Update instances of class:list #4278

sarah11918 opened this issue Aug 19, 2023 · 1 comment · Fixed by #4322
Assignees
Labels
improve documentation Enhance existing documentation (e.g. add an example, improve description) v3.0

Comments

@sarah11918
Copy link
Member

sarah11918 commented Aug 19, 2023

📚 Subject area/topic

  1. class:list directive AND 2. scoped style hashes are lowercase!

📋 Page(s) affected (or suggested, for new content)

https://docs.astro.build/en/reference/directives-reference/#classlist
https://docs.astro.build/en/core-concepts/astro-components/#the-component-template
https://docs.astro.build/en/guides/styling/

📋 General description or bullet points (if proposing new content)

@natemoo-re needs to check docs for any examples that are now counter to the class:list changes for v3.0:

Including updating some uppercase scoped style hashes e.g. class="astro-KOI4QYR5"

The above listed should be the only three pages that are possibly affected.

🖥️ Reproduction in StackBlitz (if reporting incorrect content or code samples)

none

@sarah11918 sarah11918 added improve documentation Enhance existing documentation (e.g. add an example, improve description) v3.0 labels Aug 19, 2023
@sarah11918
Copy link
Member Author

Not sure why this wasn't closed automatically, but closed by #4322 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improve documentation Enhance existing documentation (e.g. add an example, improve description) v3.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants