Skip to content
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

Update Tailwind executable call for v3.0 #5877

Merged

Conversation

forkata
Copy link
Contributor

@forkata forkata commented Oct 16, 2024

Summary

As of tailwindcss-rails >= 3.0 the command for the executable was
extracted to a separate tailwindcss-ruby gem, which causes an error in
the rake tasks we generate for the solidus_admin.

See release changelog here - https://github.com/rails/tailwindcss-rails/releases/tag/v3.0.0
and the documentation for the new gem here - https://github.com/flavorjones/tailwindcss-ruby?tab=readme-ov-file#ruby

The error this fixes is

NoMethodError: undefined method `executable' for Tailwindcss::Commands:Module

Checklist

Check out our PR guidelines for more details.

The following are mandatory for all PRs:

The following are not always needed:

  • 📖 I have updated the README to account for my changes.
  • 📑 I have documented new code with YARD.
  • 🛣️ I have opened a PR to update the guides.
  • ✅ I have added automated tests to cover my changes.
  • 📸 I have attached screenshots to demo visual changes.

@forkata forkata requested a review from a team as a code owner October 16, 2024 21:42
@forkata forkata force-pushed the chore/update-tailwind-ruby-api branch from 1c33f35 to 58ca9ea Compare October 16, 2024 21:43
@forkata
Copy link
Contributor Author

forkata commented Oct 16, 2024

The solidus_installer specs are still failing because this issue is present in the published version of solidus_admin (0.2.0).

@tvdeyen
Copy link
Member

tvdeyen commented Oct 17, 2024

Looks good. Can we make sure that we use at least v3.0 of tailwindcss-rails? In our Gemfile we still use ~> 2.0, while we allow any version in solidus_starter_frontend

@benjaminwil benjaminwil force-pushed the chore/update-tailwind-ruby-api branch from 58ca9ea to 35e8bef Compare October 17, 2024 15:08
@benjaminwil
Copy link
Contributor

@tvdeyen Thanks for catching that. I've updated the commit to include that change.

@tvdeyen tvdeyen enabled auto-merge October 17, 2024 15:13
`solidus_starter_frontend` provides templates including the
`tailwindcss-rails` gem without any version constraints. So when 3.0 was
released this week, it broke CI runs for the Solidus repository.

It appears that the only breaking change is related to the `.executable`
call.

As of `tailwindcss-rails` `>= 3.0` the command for the executable was
extracted to a separate `tailwindcss-ruby` gem, which causes an error
in the rake tasks we generate for the `solidus_admin`.

The error this fixes is:

    NoMethodError: undefined method `executable' for Tailwindcss::Commands:Module

Co-authored-by: benjamin wil <[email protected]>
auto-merge was automatically disabled October 17, 2024 16:44

Head branch was pushed to by a user without write access

@benjaminwil benjaminwil force-pushed the chore/update-tailwind-ruby-api branch from 35e8bef to 8a6f2cc Compare October 17, 2024 16:44
@tvdeyen
Copy link
Member

tvdeyen commented Oct 18, 2024

@forkata @benjaminwil I cut a new solidus_admin release. Could you please rebase this PR?

@tvdeyen tvdeyen merged commit cc57e64 into solidusio:main Oct 18, 2024
11 of 12 checks passed
@tvdeyen
Copy link
Member

tvdeyen commented Oct 18, 2024

realized we do not need a rebase. merging. thanks for fixing 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants