You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on a client app that uses store validation, it appeared that if records were already uncommitted (calling gridModel.store.addRecords() right after calling gridModel.loadData()), then they were not getting validated. Adding await wait() before adding records seems to fix the timing issue with when the StoreValidator is created.
The StoreValidator has a reaction that tracks uncommittedRecords, and we should look into firing immediately.
The first screenshot shows the initial row not appearing invalid. The second screenshot is after clicking the Add button, which then validates both records and shows the appropriate invalid display.
While working on a client app that uses store validation, it appeared that if records were already uncommitted (calling
gridModel.store.addRecords()
right after callinggridModel.loadData()
), then they were not getting validated. Addingawait wait()
before adding records seems to fix the timing issue with when theStoreValidator
is created.The
StoreValidator
has a reaction that tracks uncommittedRecords, and we should look into firing immediately.Reproduced in toolbox - see branch validateUncommittedRecords: https://github.com/xh/toolbox/tree/validateUncommittedRecords
The text was updated successfully, but these errors were encountered: