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
I'm not sure if related to this PR or not but starting to see issue with modifying final fields
(update - seeing on main - possibly may want to address after merge #2323)
I'm unable to replicate this (using comp_data_items) on master or the feature branch for #2325, @chrismclarke could you provide some more details?
This is very likely to be an issue introduced by #2312, and looking at the error in your screenshot I think the problem is to do with the row_index property (the only final property in the schemas for the persistedMemory and reactiveMemory adapters) and where that property is being saved: either at the top level of the doc or inside the data property. Potentially this is a new issue introduced by #2325 (which persists on master when data overwrites have been made on that feature branch), but probably unlikely.
The text was updated successfully, but these errors were encountered:
OK, if not replicated when working locally I'd say probably safe to close for now - could be linked to a previous local dev state. Also as these issues are not tracked in production can just reopen if replicated in the future
Extracted from the PR description of #2325:
I'm unable to replicate this (using comp_data_items) on
master
or the feature branch for #2325, @chrismclarke could you provide some more details?This is very likely to be an issue introduced by #2312, and looking at the error in your screenshot I think the problem is to do with the
row_index
property (the onlyfinal
property in the schemas for thepersistedMemory
andreactiveMemory
adapters) and where that property is being saved: either at the top level of the doc or inside thedata
property. Potentially this is a new issue introduced by #2325 (which persists on master when data overwrites have been made on that feature branch), but probably unlikely.The text was updated successfully, but these errors were encountered: