Support for debounce and throttle for index_editable fields?

[kepi]

There is currently hardcoded phx-debounce="100" for index_editable fields (text, email, number, time, date and date_time).

As for developer experience, maybe it is just me, but I was 100 % sure that setting debounce: on the field would work for inline edits and was quite surprised that it doesn't. There isn't even any special mention about this in Debounce and Throttle doc.

I'm not sure if there is some reason to have it set so aggressive, but it seems to me, at least in my application, that it should be configurable. I think that i.e. for my application "blur" is completely fine.

I'm willing to send PR if you are OK with this. But I would definitely like input on whether it should be shared debounce or we need another option like index_debounce: and index_throttle:.

[Flo0807]

Hey!

Thanks for discussing this.

I'm willing to send PR if you are OK with this. But I would definitely like input on whether it should be shared debounce or we need another option like index_debounce: and index_throttle:.

We can use a shared debounce as we already allow a function with the assigns being passed as the argument as an option. You can match on the assigns.live_action to return different debounces based on the view. See https://github.com/naymspace/backpex/blob/0.17.1/guides/fields/debounce-and-throttle.md?plain=1#L40

A PR is welcome!