diff options
author | silverwind <me@silverwind.io> | 2024-02-27 04:04:46 +0100 |
---|---|---|
committer | Earl Warren <contact@earl-warren.org> | 2024-03-06 05:10:43 +0100 |
commit | 75f7be2aacfe1ab237aa805e2b6cdcf1e646391e (patch) | |
tree | fdd2ecad61e44913b73b64ef22f6c3ae6aad4b9e /tailwind.config.js | |
parent | Fix mail template error (#29410) (diff) | |
download | forgejo-75f7be2aacfe1ab237aa805e2b6cdcf1e646391e.tar.xz forgejo-75f7be2aacfe1ab237aa805e2b6cdcf1e646391e.zip |
Apply tailwindcss rules with `!important` (#29437)
As per discussion in https://github.com/go-gitea/gitea/pull/29423, I
think this is the right way that does not burden developers having to
think about CSS precedence which should be irrelevant with an atomic CSS
framework.
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
(cherry picked from commit e55926ebfe88d6ee079842967dc7dccc2a9cdbf2)
Diffstat (limited to 'tailwind.config.js')
-rw-r--r-- | tailwind.config.js | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tailwind.config.js b/tailwind.config.js index 8c474c33a8..7f36822001 100644 --- a/tailwind.config.js +++ b/tailwind.config.js @@ -6,6 +6,7 @@ const isProduction = env.NODE_ENV !== 'development'; export default { prefix: 'tw-', + important: true, // the frameworks are mixed together, so tailwind needs to override other framework's styles content: [ isProduction && '!./templates/devtest/**/*', isProduction && '!./web_src/js/standalone/devtest.js', |