Fix Hotwire Reloading issue

[sarvaiyanidhi]

Fixes issue #99

Followed below steps for debugging Hotwire reloading issue

• Theme not getting loaded in existing mode when we change file
  On debugging on this issue, it seems like it is due to below code added in layout

<%= turbo_refreshes_with method: :morph, scroll: :preserve %>

On commenting this line, theme is getting loaded correctly in its set mode.

Also this issue on morph kirillplatonov/hotwire-livereload#33 seems to be related.

• Tailwind changes not reflecting every time on file change

On inspecting in browser console, it seems like at times we are facing with turbo link preload issue due to which changes does not get reflected in browser. To fix this issue I have added below code in development.rb. By adding below code it does not throw now issue of "the resource was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloaded intentionally"

config.action_view.preload_links_header = false

Referred this link for this issue https://stackoverflow.com/questions/72753525/rails-turbo-link-preload-but-not-used-within-a-few-seconds-from-the-windows/72901033#72901033

[tjbarber]

Marking this as Request changes for now so this doesn't get prematurely merged.

[tjbarber]

Hey @sarvaiyanidhi, we definitely want to keep turbo_refreshes_with method: :morph, scroll: :preserve. Morphing is a really cool feature of Turbo 8 that's we're going to want to utilize.

Is it possible to fix this issue with just the config.action_view.preload_links_header change?

[sarvaiyanidhi]

Thanks @tjbarber for feedback.

By just adding config.action_view.preload_links_header fixes Tailwind changes not reflecting every time on file change but theme issue still persist.

I believe theme old value is not getting retained due to morph code. I understand that we need this feature for the application but on checking further it seems like it is already identified issue. Came across related issues on the same hotwired/turbo#1210

[wassson]

Hey @sarvaiyanidhi ! We talked this one over and we think it's best to actually pursue an entirely different solution for theme switching altogether. We're considering options like persisting the state on some sort of user_settings table that we still have to map out. Thanks for putting time into this! Would you close this PR? I will close the issue as obsolete for now.

[sarvaiyanidhi]

Noted. Will close this PR.