strblr

Same error here.

Any update ?

Ok by logging the generated indices, I can see what's going on. Here are some: ``` 'Query.hypotheses(project:"61008f309a516c36b4505363",law:"2")', 'Query.hypotheses(project:"61008f309a516c36b4505363",law:"null")', 'Query.hypotheses(project:"61008f309a516c36b4505363",law:"3")' ``` Non-string values seem to be cast to strings before generating...

@n1ru4l Well since the base scalars are JSON-ish, you could use `JSON.stringify` for numbers, strings, null and booleans, and `.toString()` for other values. This would make the indices closer to...

You would still have the hard-coded double quotes, which can bring weird indices collision. For example imagine a nullable query argument of type `String`: `null` and `"null"` would serialize to...

Same problem here with `network-only`. Setting `nextFetchPolicy` to `cache-first` doesn't solve the problem : it stops from refetching "parent" data, but in fact it stops all refetching, even if variables...

Having the same problem. The infinite loop keeps on going even when the component containing the `useQuery` is unmounted. I have a `pollInterval` on my query and the query is...

I also noticed on the DatePicker : - When using date strings with value and onChange props, the internal default formats for both are not the same, causing the day...

Would love that too!