New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
<Configure /> types wrong or conflict with documentation #5989
Comments
I believe you haven't installed |
Can confirm we have been using
|
Hey, I copied your code standalone, and everything seems to be working? Is there any package that could be stuck at an older version? Even transitive ones like Here's my reproduction that has no typescript error: https://codesandbox.io/p/devbox/configure-works-nrlt73 |
Our code works because we cast |
Going from "instantsearch.js": "4.64.1" to "instantsearch.js": "4.64.3" does break types somehow. The following starts erring, telling me connectConfigure(() => {})({
searchParameters: { hitsPerPage: this.#hitsPerPage },
}) |
I don't think any change happened in those versions @flevi29, are you sure that was the only change? |
All I know is that I reverted my update only on I know that it was printing something like |
Sure, PickForClient is there to support many use cases for different versions of |
I was having the same issue. I think it might not be related to any changes within the library. Differences could potentially be, node version, yarn version or typescript version? (I was using an older version of node locally and the error was not arising). |
Did you resolve the problem on the build server in the end @Ra0R ? |
@Haroenv I did not, I used the workaround by casting it to the correct type. I am not sure what causes the issue. |
馃悰 Current behavior
In the documentation here,
https://www.algolia.com/doc/api-reference/widgets/configure/react/#widget-param-searchparameters
it outlines that you should be able to define a filter on the Configure component like so,
Which does work as expected but when implemented in Typescript the following type error appears,
'filters' does not exist in type 'PlainSearchParameters'
.Are we potentially not implementing this correctly, could it be and issue with using
react-instantsearch-nextjs
or is there a problem with the libraries types?Thanks!
馃攳 Steps to reproduce
Live reproduction
...
馃挱 Expected behavior
This is a development issue. No live preview required.
Package version
7.5.0
Operating system
No response
Browser
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: