Wait for typing to be over before requesting data

There's a debouncer built into Drupal. I didn't spot any docs but this article and this other article + referencing other uses of debounce in core should provide guidance in figuring out how to incorporate this in the Svelte app.

I'm tagging "Project Browser MVP" - while it's not critical it get into the MVP, it sounds like something the group working on the MVP would have bandwidth to address and this will make it more visible to them.

Video with debouncer

debounce video with 250 wait

I think we can use something like

  let timer
  $: text && debouncedSearch()
  function debouncedSearch() {
    clearTimeout(timer)
    timer = setTimeout(onSearch, 500)
  }

and then
on:keyup={debouncedSearch()}
This will avoid use of core/drupal.debounce library. Thoughts?

I don't see any reason we'd need to avoid the use of core/drupal.debounce library. If the library was deprecated or we were using a tiny part of a large library, it might be worth looking for ways to not use it. In this case, its use seems appropriate as code>core/drupal.debounce does exactly what we need and nothing more + it is code that has been in core for several years and proven to perform solidly.

With a +1 in #13 I think it's OK to switch back to RTBC, and we'll let the committer make the final call.

There's been some other PB issues where we've actively avoided bringing in a core library because we'd only be using a small part of a rather large library, so I understand where @narendraR was likely coming from.

I think this is the right thing. Let's not reinvent the wheel if we have it in Drupal. I see Ben's point about bringing in a giant library for one piece of it, but especially in this case where the library is lightweight, it's the right thing.

Tested with it working, 250 feels good, confirmed the request happening. Much more of what I'd actually expect here.

(Thanks for the counterpoint narendraR!)