seanpdoyle
commented
11 months ago Thank you for opening this issue.
From a Stimulus perspective, Controllers shouldn't be doing any property caching or memoization of their targets. Every time a this.[name]Target or this.[name]Targets property is accessed, the controller should query its scope to find the appropriate elements. Neither morphing nor full-page reloading shouldn't be affecting that logic, since it's a fetch each time.
With that in mind, I wonder what's preventing changes to the target's attributes during the morph. Could you share some more details about your project, particularly the changes you've layer on top of what's provided by https://github.com/stimulus-components/stimulus-rails-nested-form?
meceo
adrienpoly
julianrubisch
ghiculescu
I test page refreshes on a small project. the project uses https://github.com/stimulus-components/stimulus-rails-nested-form
I have \<template> tag that has some attributes preset. The presets change according to user actions that triggers new page content from server response. After activating morph I noticed the attribute that is used to add nested element is always the old one (tested by simply adding
console.log(this.templateTarget.innerHTML)in this line) even though the server returns new one with proper values. After full refresh the presets are correct (new ones). Before morph activation the page would reload as normal turbo (body replace) and \<template> would have correct values when adding using nested form feature.