Eric Butler
Eric Butler
If I'm [reading this correctly](https://github.com/bvaughn/react-error-boundary/blob/master/src/index.tsx#L106), `onResetKeysChange` is not triggered if you go from no error to having an error. If you change query2 to also fail, both `onResetKeysChange` are called...
In your example `onResetKeysChanged` is called during the transition from error to no error, which is when we want to invalidate the query. If within `onResetKeysChanged` you call `queryClient.clear()` instead...
> so as discussed here, it seems that `resetKeys` / `onResetKeysChanged` is not good enough: > > * [Query errors not being reset #3485 (comment)](https://github.com/TanStack/query/issues/3485#issuecomment-1093131919) > > having an effect...
The `number` type in [json-schema](https://json-schema.org/understanding-json-schema/reference/numeric#number) (and javascript) is floating point and can't be safely used to serialize decimals. This is why Pydantic serializes decimals to strings: https://docs.pydantic.dev/latest/api/standard_library_types/#decimaldecimal The schemas generated...
A possible solution might be to add an optional component like: ```tsx Open menu Menu 1 New Window Open Closed Tab Open File ```
I didn't realize that the context was exported, so this is what I've done within my app: ```tsx import { Portal, useMenuContext } from "@chakra-ui/react"; export const MenuPortal: React.FC =...