Replies: 2 comments 11 replies
-
The current Note that your app should never depend on the order of q.args/q.events as it's not guaranteed. Instead, you should handle them all regardless of the order they come - handle them as batches rather than individuals. |
Beta Was this translation helpful? Give feedback.
-
Order of The location of # in q.args can be reverted to pre-0.25.2, but this does not change that q.args order cannot be guaranteed. This will be applied to 0.25.3 which can be cut early week of 05/08. Handle_on has a series of problems that developers have ran into, but are working around and using today in their apps. To improve this functionality without breaking existing apps, a new method (something like "handle_change") will be created in the coming weeks. After developers have had sufficient time to move over, the handle_on functionality will be depreciated and removed. |
Beta Was this translation helpful? Give feedback.
-
In wave 0.24.2
Screen.Recording.2023-03-23.at.11.34.42.mov
in wave 0.25.2
Screen.Recording.2023-03-23.at.11.33.14.mov
sample code:
This behavior heavily affects apps that already use
@on()
handlers, they need to be completely revamped and tested. Any thoughts?Beta Was this translation helpful? Give feedback.
All reactions