@dixpac thank you for your contribution! @Spone has handled code reviews for generators in the past, so I've passed this one to him ❤️

Hi @dixpac! Thanks for your PR! I'm not much of a Tailwind user, can you elaborate on what's the expected behavior for the generator? I read the diff quickly and I'm not sure I understand how this differs from the regular generator?

Yeah, it is pretty much the default rails generator with tailwindcss templates.
We had to "monkey-patch/copy" it in order to support partials in Rails 6 --> https://github.com/rails/tailwindcss-rails/blob/main/lib/generators/tailwindcss/scaffold/scaffold_generator.rb#L25

Inside the engine, template name is tailwindcss so when folks are using it together with view_component they get an error
error tailwindcss [not found] when generating the component.

Generator just needs to create same files as with erb generators :)

I hope this helps :)

This would certainly be useful for those of us using tailwindcss-rails.

For others using view_component and tailwindcss-rails this workaround will keep you going.

$ bin/rails g component <Name> --template-engine=erb

@dixpac can you please rebase to resolve the conflicts, and try to fix the tests that do not pass for Rails 5?

@Spone sure I will try. Rails 5 will be a bit harder since tw-rails is rails >= 6, but we will make it work somehow :)

What do you think about using Appraisal?

You will be able to install tailwindcss-rails only for rails 6.

👋🏻 I think it's worth pursuing conditionally adding this support only in Rails >= 6, as long as we make it clear in the documentation. The Rails asset delivery story has certainly changed a bit from 5>6>7 and I think it's not unreasonable to expect folks to be reasonably up to date to use this functionality.

I tried this without success (works locally, but not in CI).

@joelhawksley would you be open to adding Appraisal? I think it's the cleanest way to implement conditional dependencies. It would also make locally running tests for all versions of Rails much easier.

@Spone I'm totally fine with adding Appraisal ❤️

@Spone Worth noting that there may be complexity getting Appraisal to fully work with Github Actions: thoughtbot/appraisal#174 (comment)
I'm slowly, painfully, ripping it out of my gems due to not getting it to run with Github Actions.

@pboling I haven't looked into it in detail yet, but I know we're using Appraisal + Github Actions to test https://github.com/pantographe/view_component-form without issues.

Is still useful with the new tailwindcss-rails?

@coder2000 yes. If you want to "attack" adding Appraisal that would be awesome

Hi @dixpac, Appraisal is now setup and I used it in your PR to manage the conditional dependency to tailwindcss-rails.

👏🏼 @Spone thank you! I'll bump and resolve the conflict

@Spone version bumped, conflicts fixed, squashed and I've added you as a co-author :)