Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8709 +/- ##
=======================================
Coverage 99.08% 99.08%
=======================================
Files 139 139
Lines 4046 4046
=======================================
Hits 4009 4009
Misses 37 37 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
11c4e9e to
4d2b2d1
Compare
5e6685d to
99c9780
Compare
e8154c9 to
7b44d57
Compare
16a5e61 to
2916f72
Compare
2916f72 to
e131141
Compare
e131141 to
5bf67d5
Compare
5bf67d5 to
92fd144
Compare
|
https://github.com/flavorjones/tailwindcss-ruby/blob/fc3c88dcb127e23f8d8bf85d081495469ce4e565/rakelib/package.rake#L71 - it is just download tailwindcss binaries, which sits in npm packages and pack it's in gems. It don't have "ruby port of tailwind" or something else. In any case you can point command "build:css" in package.json to any tailwindcss binary source - from npm or ruby, it is not a big deal |
Still requires you to have The tailwindcss cli for specific platforms is pre-compiled with bun and does not need node or npm. This is a pretty common pattern for Rubygems to do for gems that integrate with other binaries etc. The best example for this is |
|
Also with that mindset, we should just add a |
e682732 to
7b37f90
Compare
c093d38 to
184dbab
Compare
This comment has been minimized.
This comment has been minimized.
705336d to
d42f083
Compare
1a29654 to
c98983e
Compare
javierjulio
left a comment
There was a problem hiding this comment.
@tagliala thank you for all your help here. I've pushed some additional changes for Tailwind v4 support.
I believe we only have 2 items left to address here but I didn't have time to tackle today:
- Address the outline-none instances on review
- Upgrade Flowbite from v2 to v3 for Tailwind v4 support
- Remove tailwind v3 downgrade from test-application - Use tailwind cli to compile css - Delete generated files that are not used - Add a reference to old javascript config file - Remove `@tailwind` directive - Remove config argument when adding `build:css` script to test app - Rename deprecated utilities https://tailwindcss.com/docs/upgrade-guide#renamed-utilities
Use v4's `scheme-dark` to fix icon colors on some native inputs Ref: https://v3.tailwindcss.com/docs/v4-beta#color-scheme-utilities
Ran this last to account for any other changes.
c98983e to
4543bd8
Compare
javierjulio
left a comment
There was a problem hiding this comment.
Thanks! I'll leave this for you @tagliala to merge if you have nothing else to change.
|
Hello, thank you everyone for the interest in this feature ActiveAdmin v4.0.0-beta19 has been released with Tailwind v4 Please do not hesitate to provide feedback |
|
Great job, team! |
Upgrading: https://github.com/activeadmin/activeadmin/blob/master/UPGRADING.md#upgrading-from-earlier-4x-beta-to-400beta19
@tailwinddirectivebuild:cssscript to test apphttps://tailwindcss.com/docs/upgrade-guide#renamed-utilities
TODO:
"type": "module",to app'spackage.json? 3bfb95e#r1972531187Not from scratch, this is being done by cssbundling railstailwindcss@clishould be installed as a dev dependency?Additionally:
scheme-darkon input fields when dark mode is enabledBefore
After