docs(readme): Correct casing of @Sage scope #338
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adrianbruntonsagecom
changed the title
adrianbruntonsagecom
force-pushed
the
amend-docs-sage-casing
branch
from
f48a233 to
cdd0736
Compare
adrianbruntonsagecom
force-pushed
the
amend-docs-sage-casing
branch
from
cdd0736 to
c76ddea
Compare
druhill
approved these changes
Nov 24, 2023
|
🎉 This PR is included in version 4.32.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When importing CSS using the documented path of
@import "@Sage/design-tokens/css/base.css";, a vite build results in an error:This was due to a casing issue in case sensitive operating systems - it occurred in GitHub actions running under a linux environment. This change amends the documentation to be consistent by specifying a lower cased "@Sage" scope.