[Bug] Repeatable - know which row triggered the ajax request

Bug report

What I did

Setup a repeatable with ajax fields using include_all_form_fields to manipulate the returned results based on form condition.

What I expected to happen

When user has for example 2 rows, I expect to have a way to know which of those rows triggered the request to the endpoint.

What happened

I can’t know which row triggered the ajax request.

What I’ve already tried to fix it

Nothing yet, but I think we can use the newly added backpack_field.parse_value event in repeatable #3439 to add two hidden fields to the form, one with repeatable_name and other with repeatable_row so in the end we know which select triggered the request. Maybe add another event backpack_field.parse_value_finished that will remove those fields from the form again.

Backpack, Laravel, PHP, DB version

When I run php artisan backpack:version the output is:

[pxpm]

Hey @tabacitu I am not sure we should postpone this to 4.2. It’s not a BC, it’s atleast an issue that makes repeatable fields behave different than the others. And aiming at having the editable pivot fields #3410 in 4.1 (along with fixing the relationships) this becomes like a must in the field, otherwise it would break in very common scenarios I think (and then it would become a real bug).

I plan to merge the other repeatable PR’s (rows, dependants etc) and only after tackle this one. And I think we are done with repeatable (atleast we gave it the functionality we support in other crud fields).

Rephrasing, what I think is that if we are going to put repeatable in the spotlights, we should make it work 100%, atleast in the scenarios we already are aware of.

Let me know, Pedro

[pxpm]

There is a PR for this already open. I am going to close this issue. #3439