-
Notifications
You must be signed in to change notification settings - Fork 36
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
[feat] change privacy-policy class style to tailwind inlines #512
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ephemeral-sable-89c7e0 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.
Awesome works! And it fits well at my local.
However "important" this part is new to me. Let me see if someone more experienced than me can check.
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
@@ -4,6 +4,7 @@ module.exports = { | |||
mode: 'jit', | |||
purge: [], | |||
darkMode: false, // or 'media' or 'class' | |||
important: true, |
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.
Due to this config may affected all site of css, we cannot guarantee that all page is correct.
I don't think it's a good idea to add important in every tailwind generated css.
If we're going to migrate scss to tailwind, then maybe we should have a migration plan or review the new code and refactor to tailwind in every new PRs of new code.
Types of changes
Description
important: true
intailwind.config.js
to make switching to tailwind css convention easier(see Define Style coding convention #396)
Related Issue
#499
Additional context
This PR is a prove of concept as discussed in #511.