Eric Butler
Eric Butler
If anyone here is using `plugin:@typescript-eslint/recommended-requiring-type-checking` there's a known incompatibility: https://github.com/typescript-eslint/typescript-eslint/issues/4694#issuecomment-1075389608
Hi, I rebased @sofiyevsr's fixes and added the additional test requested by @sztadii: https://github.com/codebutler/chakra-ui/commit/33c1343b7c014d2a617e0f879ce083b8e7b76af6 can we please get this in? thanks
Hi, I'm no longer working with this project so I'm closing this. PR I agree that most (all?) of these uses cases can be handled by a custom mock server...
I am noticing that the behavior is inconsistent based on the order things happen. If a modal is displayed immediately when the page loads, toasts will appear above the overlay....
Hi @TkDodo @tannerlinsley, I think this issue was closed too soon. The [example](https://codesandbox.io/s/naughty-nash-7jixq?file=/src/App.tsx) above from @TkDodo only works because the "hide" state does not also have a query. This is...
Thanks for taking another look at this! I think you would need to put different `key`s on each `QueryErrorResetBoundary` in your updated example for react to create a new instance...
> https://codesandbox.io/s/suspicious-wilson-reie3j?file=/src/App.tsx You have a typo in here: ```diff - const reset = useQueryErrorResetBoundary(); + const { reset } = useQueryErrorResetBoundary(); ``` ...but that also doesn't fix the problem unless...