I am encountering the same problem that @vangelov reported two years ago, as referenced in this previous discussion. The topic was closed without any clarification regarding this potential issue. Could you kindly provide an update on when this bug might be rectified?
1 Like
Hi @saldmy,
Thanks for checking in on this bug. On v3.36, we fixed a bug where the error
value of JS queries wasn't updating correctly. This fix got us closer to a solution, but we still have an outstanding bug where .trigger()
always resolves, so it still doesn't throw an error in the catch block. I don't have an eta on that bug, but I will let you know if we ship a fix
1 Like