-
# Bug Report
## Describe the bug
`dispatchEvent` before `morph` mostly for same reflex in sequence (or not). This occured after I upgraded from 3.3.0 version. I adjust stimulus `targets` to ne…
-
-
# Feature Request
In the lifecycle, if the element was morphed out of existence StimulusReflex warns the user that the element is no longer there and that we should move the reflex higher up.
Wha…
-
# Bug Report
## Describe the bug
When you call the reflex to remove clicked element from `dom`, `afterReflex` callback won't ba called.
I suspect it's because `element` in `dispatchLifecycle…
-
I managed to launch my StimulusReflex application on IE11, but I can’t start the component, I get the error: CableReady detected an error in morph! Failed to get the "nodeType" property of a link whos…
-
# Bug Report
## Describe the bug
When using StimulusReflex with Rails 6.0.3.4 from a Rails engine, I get the error on a StimulusReflex::Channel#receive:
```shell
StimulusReflex::Channel Fai…
-
# Feature Request
It would be nice if StimulusReflex offered better logging tooling that was comfortably in-between "way too verbose" and "totally suppressed".
## Is your feature request related…
-
Getting an error when trying to use ViewComponentReflex. I have ViewComponents, Stimulus and StimulusReflex working but getting this error after installing ViewComponentReflex and trying to render a c…
-
# Bug Report
Issue that just seemed to crop up after upgrading Ruby + Stimulus Reflex.
I am using the content_reloader via the tutorial here. The only difference is that instead of using `fet…
-
# Bug Report
## Original pretense:
If you run a page morph reflex multiple times, any lazy-loaded associations in the controller action are cached, even if the data is mutated in the Reflex acti…