On Input Event

[ZktSn0w]

Hey there, i'd like to control the whole fetch logic on my own, is there any way to listen to the input change itself, not select, and then update the options?

[mskocik]

Sure, just add eventlistener to underlying <input> element. Just add inputId prop to be able to get that element easily.

Why do you need to control the whole fetch logic by yourself? What is missing that you would need?

[ZktSn0w]

I don't think it is a good way of handling such behavior that way!
Since this library is using svelte, it should use all its power.
If we are supposed to add an event listener you would have to have to:

1. Make sure the id/classes or whatever element you are using is always the same, or else it will break if some day someone adjusts it in the library code
2. manually check if the element exists and maybe wait for it,

All of this would not be needed if we implement it fully in svelte via bindables and effects.

We have a bit of complex data structure,
We have to fetch data only if ceirtain criterias are matched.
And conditionally setting or unsetting the fetch url is not clean imho
But let me know what you thinkg

[ZktSn0w]

I made an PR #306 to handle this behavior in a fully svelte reactive way
You might add some improvements to the code, it surely isn't perfect.

[mskocik]

I don't understand this part:

We have a bit of complex data structure,
We have to fetch data only if ceirtain criterias are matched.
And conditionally setting or unsetting the fetch url is not clean imho

Show me simplified example, how would you want/nned to use it? You would want to customize fetch url based on input text? Why and how customized? I need to understand to determine, if your use case and PR makes sense and is useful for the library itself.

[ZktSn0w]

Okay,
First, i would want to only fetch data when more then n Characters are entered.

Second: i have to determine the fetch url by the user input.

And third, the value of, in your case [query], must be modified.
Thats why i‘d like to have the possibility of full control over fetching and so ony

Selecting the element with document queryselector isn‘t a good option in my opinion since we are already using svelte, snd svelte provides these functionalities via bindables etc.

Hope this helps

[mskocik]

There is an undocumented low level global config property requestFactory which can be extended/customized. I believe you can achieve what you need with it. Check this REPL for simple demonstration

[ZktSn0w]

hm okay i will take a look into that thx