Adrien Foulon
Adrien Foulon
See also #421 Duplicate of #422
@nyatalieee Sure, conflict resolved
Or you are using a proxy and overwriting the content type or not proxying the X-Inertia headers, there is a lot of possible causes and without additional info it's impossible...
Your best bet for now is to store a copy of the props and update them/merge them manually when the original changes Otherwise https://github.com/inertiajs/inertia/pull/1247 would solve this
Because if you implement a modal you usually need a lazy prop `modal` under which you provide the modal data, But this modal might have itself lazy data that you...
Gave it a try and yes, the issue is that `Arr::undot` will not handle correctly `only: ['modal.lazyProp', 'modal']` (If you want to reload both the lazy and the normal props...
Yes inertia works with browser history, but it seems inertia is missing a check, so that redirects to a different domain are handled correctly and reload the page
@MooseSaeed As a workaround you can add to your HandleInertiaRequests middleware ```php public function version(Request $request): string { return md5($request->host) . parent::version($request); } ``` And if you have CORS working,...
It seems the tracking is working and the issue is with the Facebook Pixel Helper extension not detecting the events when the fetch is proxied through a service worker, the...
https://github.com/http-party/http-server/pull/687 or #282 Would solve this Ground was laid in #28 but was missing the cli options This is a much requested feature: Related: #684 #281