-
Notifications
You must be signed in to change notification settings - Fork 1
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
Style(repo): Replace unicode "heavy check mark" with "check mark" #1436
Conversation
✅ Deploy Preview for spirit-design-system ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for spirit-design-system-storybook 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.
LGTM, if we merge this now, we will have a lot of fun rebasing the release branch :D
I think, I can wait. The agreement was what I needed so I can do this after the major release. |
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.
LGTM ✓
* we have previously used "heavy check mark" unicode character that is not recognized by the Prettier v3 * @see: https://www.compart.com/en/unicode/U+2714 * this unicode character is replaced by "check mark" that is lighter and Prettier to not have problem with it * @see: https://www.compart.com/en/unicode/U+2713 * it is also more convenient to use the same size of the character because as oposite to the "check mark" we are using "multiplication" * @see: https://www.compart.com/en/unicode/U+2715 * @see: prettier/prettier#15572 for more details about the Prettier problem with thiunicode character
8e8c293
to
57edc34
Compare
Description
that is not recognized by the Prettier v3
and Prettier do not have a problem with it
because as opposed to the "check mark" we are using "multiplication"
details about the Prettier problem with the Unicode character
Additional context
This modification is necessary for #1021 to be merged.
Issue reference