- Issue created by @v.koval
- last update
over 1 year ago Build Successful - @vkoval opened merge request.
- Status changed to Needs review
over 1 year ago 1:00pm 11 August 2023 - last update
over 1 year ago Build Successful - last update
over 1 year ago Build Successful - last update
over 1 year ago Build Successful - last update
over 1 year ago Build Successful - last update
over 1 year ago Build Successful - πΊπ¦Ukraine v.koval
I noticed another bug - when I add a new item, the ajax is triggered, and the path in the autocomplete also returns to the default value, despite the fact that the value in the select list is completely different. So I propose a new patch
- π¨π¦Canada jibran Toronto, Canada
Can we add test for this? There is a functional JavaScript test we could update.
- πΊπ¦Ukraine v.koval
Hello!
I'm not sure that we need to add a test for this case. After all, this is not a new feature, but only a bug fix. But if you have ideas on how to write a test for this case, that's great - πΊπ¦Ukraine v.koval
Hi!
Any news?
I think it's a significant bug, it would be nice to have it released - last update
over 1 year ago Build Successful - last update
over 1 year ago Build Successful - last update
over 1 year ago Build Successful - last update
about 1 year ago Patch Failed to Apply - First commit to issue fork.
- Merge request !27Update autocomplete path on page reload or Ajax trigger. β (Open) created by amourow
- πΉπΌTaiwan amourow
The above code works well and resolved the issue that v.koval described.
I made a merge with the above fixes request for the 3.x-dev version.Please help reviewing the code.
- πΉπΌTaiwan amourow
amourow β changed the visibility of the branch 3380619-data-autocompplete-path-4.x to hidden.
- Merge request !28Update autocomplete path on page reload or Ajax trigger. β (Open) created by amourow
- πΉπΌTaiwan amourow
amourow β changed the visibility of the branch 3380619-data-autocompplete-path-4.x to active.