douglas

I ended up having to update my test project to only use loading of turbo-rails through the tag helper...after I did that it worked as it did before https://gitlab.com/doug.stull/turbo_modal/-/commit/ce17a5208fb175f3ffe8c5e40ed4031f18ca9f08

It seems that upgrading past turbo-rails version 0.5.3 is an issue. Using tips from this episode, form submission is now submitting as html again instead of TURBO_STREAM. This causes an issue when create needs to re-render on save failure as seen in this path - https://github.com/gorails-screencasts/hotwire-twitter-clone/blob/master/app/controllers/tweets_controller.rb#L35

Anyone else have issues when using turbo-rails 0.5.4 and up? The change seems to be around this commit https://github.com/hotwired/turbo-rails/commit/b3fab95cc3e73b1a2960f0ea4a3509e0d490a16a#diff-a6c9ea9b91a99345ff04b9597b41369bc2552724c7c00135db376ff782aaf7ab

I had the same issue. Loading issue concerning application controller.

I put the turbo controller in the controllers dir in turbo_controller.rb and issue was resolved

interesting replacement for cocoon. Wondering, does anyone see something here that cocoon does cover and this does not? Weighing options here, and want to be wary of moving away from the mature cocoon implementation and perhaps missing some implicit functionality it offers, gotchas, etc that this may not cover.

side note:
I have implemented a text_field_tag version of this using stimulus where it wasn't attached to a nested association directly and used a similar setup to this...template is a cool alternative to building the inputs in JS - thanks!