Stimulus Behaviors: stimulus-use

hey Peter L.

That is pretty good example! Thx for sharing it!

Cheers!

Hey Kirill,

Thank you for sharing a link to BC notes in V3 of Stimulus, it might be useful for others.

Cheers!

using the beta version hepled, but it is not possible to use useDebounce, because of this bug:

https://github.com/stimulus...

any workarounds for that?

Thanks

Ok, I just had to think about it for a second myself. The workaround is easy and quite obvious.

Instead of:

const params = new URLSearchParams({
    speaker: event.currentTarget.value,
    preview: 1,
});

Is just use:

const params = new URLSearchParams({
    speaker: this.inputTarget.value,
    preview: 1,
});

and add the data-search-preview-target="result" attribute to the input-field and add input to the static targets so there is no need to use currentTarget anymore.

Hey Tristano,

So you basically need to replace "event.currentTarget" with "this.inputTarget". Thank you for sharing this solution with others!

Cheers!

Hey Ruslan!

Ah, sorry about the troubles! The stimulus-use library has support for Stimulus v3, however they haven't created a tag yet, and I'm not sure why :/. Try running yarn add stimulus-use@beta --dev to get their beta version, which should support it.

Cheers!

I had the same problem. But I kind of "complicated" my setting using yarn workspaces (multiple package.json's and multiple webpack configs, etc). But I narrowed it down to stimulus-use (for useDispatch).
Ryan's solution worked for me:

`"stimulus-use": "^0.50.0-2",`

Hi ,
Thank you. It helps. After yarn add stimulus-use@beta --dev
We can see "stimulus-use": "^0.50.0-2" in package.json

Hello Kevin,

I had the same problem.

I fixed it by removing the parameter from my function search().
I use a target on my input tag to catch my parameter.

<input
    name="q"
    value="{{ searchTerm }}"
    placeholder="Search products..."
    type="search"
    class="form-control"
    data-action="search-preview#onSearchInput"
    data-search-preview-target="input" {# Add a target #}
>

So I can use my search function without parameter :

import { Controller } from '@hotwired/stimulus';
import { useClickOutside, useDebounce } from 'stimulus-use';

export default class extends Controller {
  static values = {
    url: String,
  }

  static targets = ['result', 'input']; // Add the target
  static debounces = ['search'];

  connect() {
    useClickOutside(this);
    useDebounce(this);
  }

  onSearchInput(event) {
    this.search();
  }

  async search() { // Remove parameter
    
    const params = new URLSearchParams({
      q: this.inputTarget.value, // Use the target vlaue
      preview: 1,
    });
    
    const response = await fetch(`${this.urlValue}?${params.toString()}`);

    this.resultTarget.innerHTML = await response.text();
  }

  clickOutside(event) {
    this.resultTarget.innerHTML = '';
  }
}

I hope this helps!

This worked for me, thank you @cctaborin

Hi,
I faced the same problem and made it work by passing the value inside an array, I hope it helps:

onSearchInput(event) {
   this.search([event.currentTarget.value]);
}

Hey everyone!

This problem is due to a "fix" introduced in stimulus-use 0.51.2! See the answer from @Giuseppe-P for details - https://symfonycasts.com/screencast/stimulus/stimulus-use#comment-29400

And I'll add a note :)

UPDATE: Hmm, I'm having some DIFFERENT trouble now with that solution. I'd love to know if it works for someone else - I think this is a bug on stimulus-use and I'm working on a reproducer. It seems you need to call this.search({params: event.currentTarget.value})<br /> AND then in search(), change to query.params... which all seems a bit nuts :)

Cheers!

Hey @weaverryan I got some issues too..
Here my search-preview_controller:

import { Controller } from "@hotwired/stimulus";
import { useClickOutside, useDebounce } from "stimulus-use";

export default class extends Controller {
    static values = {
        url: String,
    }
    static targets = ['result'];
    static debounces = ['search'];
    connect() {
        useClickOutside(this);
        useDebounce(this);
    }
    onSearchInput(event) {
        this.search({params: event.currentTarget.value})
    }
    async search(query) {
        const params = new URLSearchParams({
            q: query,
            preview: 1,
        });
        const response = await fetch(`${this.urlValue}?${params.toString()}`);
        this.resultTarget.innerHTML = await response.text();
    }
    clickOutside(event) {
        this.resultTarget.innerHTML = '';
    }
}

So I don't have the issue mentionned about the params, but... No results.
Before using debounce, the result was fine.

Any idea ? Do you think it's linked ?

Thanks!

Hey @Christina-V!

After adding that comment, I looked deeper and it seems like the solution may NOT be so simple. I think the latest version of useDebounce is plain broken. I added a comment about it on the issue - https://github.com/stimulus-use/stimulus-use/issues/295#issuecomment-1520768400 - if we're able to get your example working - you could comment on there to help push that along :).

So, you are correctly (according to the current way that useDebounce() works) are passing {params: event.currentTarget.value} to this.search(). The 2nd part of the equation, I believe, is that your search() method needs to accept this whole object. So:

async search(searchOptions) {
    const params = new URLSearchParams({
        q: searchOptions.params,
        preview: 1,
    });

    // ...
}

That's horribly ugly and wrong... but I believe that's what's needed. In summary, here is how it seems to currently work:

A) When you call a debounced method, you must pass an object with a params key on it
B) Then, that entire object is passed to your method... so you need to read the .params key back out to get the original value.

Again, if my workaround works for you, I'd love if you could comment on the issue about what work-around you needed to add.

Thanks!

@weaverryan,

I can confirm the situation you describe !
I was eager to use my debounced onSearchInput method after the tutorial update, but it turns out that the search feature in my app is "broken" like @Christina-V 's one : no error in the console but an empty result from my Symfony app...

When I step-debugged in my Symfony Controller, what is send to PHP (if you keep the code as-is in the search function) is the string "[object Object]" : good luck to find anything with this search term 😅

So yeah, like you, I receive the whole params object in my search function and I had to change my function to what you shared...

I may switch to the cctaborin's solution that is based on the Values API...

Thanks all for the debug inquiry (and Ryan for this in-depth tutorial AND follow-up)

Thank you for confirming! I'm now convinced we've understood and described the situation correctly. Hopefully we'll get some movement on the issue - https://github.com/stimulus-use/stimulus-use/issues/295

And yes, the solution from cctaborin's looks solid - https://symfonycasts.com/screencast/stimulus/stimulus-use#comment-29193

Cheers!

Hello Kevin,

I have the same problem. Have you already found a solution for this?

Thanks

Hey Ludwig,
Never got to the bottom of it and had to move on.
Good luck.

-Kevin

Hey Kevin,

Seems you messed up in that DebounceController implementation. I'd recommend you to dump the data you're working with there using console.log() feature and see the data in the Chrome Console. For example, add console.log(params); to make sure the value of that variable is exactly what you're supposed to handle in that spot. And so on, dump more vars to make sure you're working with correct data there. When you will see what data you're working with - I think it will give you some glue... otherwise, it's difficult to say.

I hope this helps!

Cheers!

Hey Vic!
Appreciate your response. The DebounceController is not mine, that's right out of the stimulus-use library, I was just posting it for reference. And, you're probably right, something is goofy there. :)

Hey Kevin,

Oh, I got it ) Hm, then it should be OK... probably you messed up with its configuration? Did you check official docs?

Cheers!

I've checked the source code: from v0.50 it seems the debounce wants an object with a params property:

use-debounce.ts

const args = Array.from(arguments)
const params = args.map(arg => arg.params)

So I fixed with:

onSearchInput(event) {
    this.search({params: event.currentTarget.value})
 }

v0.41 arguments was taken, so in the video passing event.currentTarget.value directly seems ok.

const args = arguments

Ah, righteous! Thank you @Giuseppe-P!

This was changed in 0.51.2, of all random versions :p. Here is the PR https://github.com/stimulus-use/stimulus-use/pull/252

I'll add a note!

Hey Giuseppe,

Thank you for sharing this tip! Seems some BC breaks were introduced in a newer version, we will add a note.

Cheers!

I just found the solution, it requires installing hotkeys.js. Hope this helps those who are going to encounter this problem. Thanks for your great tutorials !!!!

Never mind. I got it. Because i use ddev i installed stimulus-use in the wrong directories.
Thanks for your great tutorials!