Prioritize custom view templates

[mojodojo101]

Current behavior:
Custom templates are ignored by the tailwindcss-rails generator

Expected behavior:
View templates under "#{RAILS_ROOT}/lib/templates/erb/scaffold" should be prioritized by the generator.

#164

[flavorjones]

@mojodojo101 Thanks for submitting this. CI is failing, can you look into it, please?

[mojodojo101]

@mojodojo101 Thanks for submitting this. CI is failing, can you look into it, please?

Hmm, i guess Rails.root isnt initialized in those tests, would it be fine to simply check if its nil with an if statement or is that piece of code i wrote just rubbish?

[flavorjones]

Can you please remove the version bump and changelog entry from this PR to avoid conflicts?

Would it be possible to write a test to describe the behavior you're introducing?

[mojodojo101]

I removed the Changelog and Version bump 😄 . I dont know much about writing tests/ integration tests so i might have to look into that once i have some time on my hands.

The tldr of the behavior introduced here is:

• Check if there is a /lib/templates/erb/scaffold folder in rails
• If that is the case use the templates in that scaffold folder rather than the folder provided by tailwindcss-rails

Following the procedure that is described here

https://guides.rubyonrails.org/generators.html :
... Another common use of custom templates is overriding the default scaffold view templates. You can override any of these by creating the appropriate file (e.g. index.html.erb, show.html.erb, etc) in lib/templates/erb/scaffold.

---

At the moment it just checks if the folder is there, if we want file granularity, this commit wont do just fyi.

[rgarver]

I just hit this issue. Is there any additional work required to make this mergeable?

[flavorjones]

I'm closing this in preference of #314 which is a simpler fix and has test coverage.