@seanpdoyle described a number of exciting, and intriguing points here in this PR:
hotwired/turbo-rails#257 (comment)
For example, his data-confirm implementation excites me since I currently have a very hacky data-async-confirm solution. In addition, there are many other items such as respecting frames on form submissions that is important for working in a Turbo enabled app.
There are some things that may not apply. For example, data-method in mrujs constructs a Fetch request under the hood and does not actually submit a full form, as well as some turbo-specific things such as request-start since mrujs will handle its own lifecycle of ajax: events this may not be necessary.
Regardless, over the next few days I plan to go in and pluck key points out from his post / PR and hope to start implementing some of these features into Mrujs since theyre exciting to me and I think they should be considered.
@seanpdoyle described a number of exciting, and intriguing points here in this PR:
hotwired/turbo-rails#257 (comment)
For example, his
data-confirmimplementation excites me since I currently have a very hackydata-async-confirmsolution. In addition, there are many other items such as respecting frames on form submissions that is important for working in a Turbo enabled app.There are some things that may not apply. For example,
data-methodin mrujs constructs a Fetch request under the hood and does not actually submit a full form, as well as some turbo-specific things such asrequest-startsince mrujs will handle its own lifecycle ofajax:events this may not be necessary.Regardless, over the next few days I plan to go in and pluck key points out from his post / PR and hope to start implementing some of these features into Mrujs since theyre exciting to me and I think they should be considered.