Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to pass autocomplete timeout as a parameter #533

Closed
martinjedwabny opened this issue Oct 16, 2023 · 3 comments
Closed

Ability to pass autocomplete timeout as a parameter #533

martinjedwabny opened this issue Oct 16, 2023 · 3 comments
Labels
kind: Enhancement 📈 New feature or request what: Configuration Related to how the component is configured what: Widgets Related to component value selection widgets

Comments

@martinjedwabny
Copy link

Description
I have an use-case with a big knowledge base in which the autocomplete fails to get the dropdown data due to a 7 second timeout for the autocomplete widget.

Desired behaviour
I would like to be able to pass the timeout time in ms as an optional parameter of sparnatural.

File + line with the timeout:

@tfrancart
Copy link
Contributor

Thanks ! yes good idea. We will be working in general on the autocomplete widget in the next few months. This raises the more general question of how to customize the behaviors of widgets, as more and more parameters will be needed; we probably need a general framework for that.

@tfrancart tfrancart added kind: Enhancement 📈 New feature or request what: Widgets Related to component value selection widgets what: Configuration Related to how the component is configured labels Oct 16, 2023
@tfrancart
Copy link
Contributor

As a workaround, have you tried optimizing the datasource of the widget, in order to tune the SPARQL query that is being sent to fetch the autocomplete values ? this could make it below the 7s threshold maybe ?

@tfrancart
Copy link
Contributor

Now that we don't rely on easyautocomplete, but rather on the fetch method of the browser, the default timeout being used is much higher. This would be the default timeout of the browser, which should be around 1 minute or 30 seconds, depending on the browser.
I will thus close the issue, feel free to reopen if needed after testing with the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: Enhancement 📈 New feature or request what: Configuration Related to how the component is configured what: Widgets Related to component value selection widgets
Projects
None yet
Development

No branches or pull requests

2 participants