We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi!
It's me again. I've been curious to implement the latest version of your great library!
However, I encountered a little issue when hosting the data.
It looks like the URL is not correctly inferred.
After a little investigation, I guess that the issue comes from here:
infisearch/packages/search/lib/worker/workerSearcher.ts
Line 63 in 0dc60ce
Where the innerUrl already has a /
innerUrl
/
Line 90 in 0dc60ce
For an obscure reason, no problem for local dev, but once deployed, the search-ui fails to load the data :/
The text was updated successfully, but these errors were encountered:
Thanks for the catch! And even pinpointing the exact line.
I've just released a new version with extra / removed.
I'm guessing it's based on the server. (Github pages seems to be doing some auto-correction for example)
I'll leave this open to make a note of updating the e2e tests to handle this.
Sorry, something went wrong.
Thanks for updating it so fast 😄
I'll continue the update right now thanks to you !
No branches or pull requests
Hi!
It's me again.
I've been curious to implement the latest version of your great library!
However, I encountered a little issue when hosting the data.
It looks like the URL is not correctly inferred.
After a little investigation, I guess that the issue comes from here:
infisearch/packages/search/lib/worker/workerSearcher.ts
Line 63 in 0dc60ce
Where the
innerUrl
already has a/
infisearch/packages/search/lib/worker/workerSearcher.ts
Line 90 in 0dc60ce
For an obscure reason, no problem for local dev, but once deployed, the search-ui fails to load the data :/
The text was updated successfully, but these errors were encountered: