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
In general we rely on keeping one copy of canonical data in a baseRecordData, and then having projections modify and read from the baseRecordData. This in general works, but in cases of nested records and nested arrays, we also have childRecordDatas in both baseRecordData and the projection. While changing individual properties on those nested records will work, if you add or remove entire records from the array childRecordDatas might get out of sync between the base and projection records. I fixed one of the issues in #884 but it's likely there are more similar ones.
The text was updated successfully, but these errors were encountered:
In general we rely on keeping one copy of canonical data in a baseRecordData, and then having projections modify and read from the baseRecordData. This in general works, but in cases of nested records and nested arrays, we also have childRecordDatas in both baseRecordData and the projection. While changing individual properties on those nested records will work, if you add or remove entire records from the array childRecordDatas might get out of sync between the base and projection records. I fixed one of the issues in #884 but it's likely there are more similar ones.
The text was updated successfully, but these errors were encountered: