Open kamakshibhat-appsmith opened 5 months ago
@kamakshibhat-appsmith this is a critical issue right because this used to work before and now all apps with this will be broken. @vsvamsi1 @rajatagrawal did any recent evaluation changes impact this?
We checked on v1.11 as well and issue seems to be there as well. Not completely sure when this got introduced . Also, this won't be categorized as critical, since it doesn't seem to have impact on Deploy mode. Also, the issue goes away on refresh. This only happens the first time when JS object is created and used in a widget
It seems to be an existing issue and not from our evaluations optimisations which were made during Feb 2024. After investigating the issue i noticed that the evaluation order appears to be incorrect, the JS action is not linked to the text widget's binding. My hunch is that when dropping a new widget the dependencyMap is not updated correctly. My suggestion would be to look at subTreeSortOrder
within setupTree
and see why the evaluationOrder over here does not link with the text widget's binding.
The issue can be reproduced in v1.11 which is before evaluations performance began
@kamakshibhat-appsmith Could you please confirm if this is still reproducible? cc: @vsvamsi1
@rishabhrathod01 yes it is still reproducible
Is there an existing issue for this?
Description
Evaluations not taking place when the JS Function is freshly created and bound to a widget .
### Adding medium priority, since the issue goes away on refresh
Steps To Reproduce
https://www.loom.com/share/21c9578fb3e64144a81ca684bd9ba37b
### Adding medium priority, since the issue goes away on refresh
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
Cloud/Selfhosted (also reproducible on v1.11)