Stanislav Iliev
Stanislav Iliev
I managed to temporarily solve the problem by wrapping my modals in [React.lazy](https://reactjs.org/docs/code-splitting.html#reactlazy) and dynamically importing them. They open dynamically anyway so this doesn't affect SSR. Depending on your case...
This won't be supported.
Cleaning up, please open a new pull request if you feel like finishing this feature.
I have an `action` that starts a `setInterval` that calls fetch and for me this reproduces the error every few requests. Luckily reverting `@remix-run/web-fetch` back to 4.3.1 fixes the issue.
@moltar We shouldn't be exposing the `MWSApiError` codec, only this type: ```declare type MWSApiError = GetInterface;``` > What would be then a good choice that solves these problems If this...
@octogonz TypeScript is able to differentiate between values and types of the same name. In this case `const MWSApiError` and `type MWSApiError` are two different things and are neither self-referential...
Unfortunately I can't unpublish that version so I've deprecated it. I'm on vacation so I'm not able to publish a quick fix.
Reverting the changes in this PR https://github.com/software-mansion/react-native-gesture-handler/pull/3295 using patch-package fixed the issue for me.
Yes, this is desirable behaviour. It's not part of the docs, unfortunately, you are correct. >On a related point, when the callbacks of the Either methods .map and .chain throw...
I think both, users should know about this behaviour, but shouldn't abuse it.