Kenneth Kimari
Results
2
comments of
Kenneth Kimari
This happened to me too on the new `inertiajs/inertia` v1.0. I would just like to understand why the `setData` function behaves that way.
So apparently, this is not a bug but due to the behavior of `state` in React