forks/forgejo
1
0
Fork 0
Code Releases Activity

Apply tailwindcss rules with !important (#29437)

Browse source 
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)
This commit is contained in:
silverwind 2024-02-27 04:04:46 +01:00 committed by Earl Warren
parent 8f3ef5aa71
commit 75f7be2aac
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
tailwind.config.js
View file

@ -6,6 +6,7 @@ const isProduction = env.NODE_ENV !== 'development';
export default { export default {
prefix: 'tw-', prefix: 'tw-',
important: true, // the frameworks are mixed together, so tailwind needs to override other framework's styles
content: [ content: [
isProduction && '!./templates/devtest/**/*', isProduction && '!./templates/devtest/**/*',
isProduction && '!./web_src/js/standalone/devtest.js', isProduction && '!./web_src/js/standalone/devtest.js',