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
key and _objectKey are fields, which have a special meaning for this project.
key
It is a field, that has to be set to every row in antd table as its unique identifier. For that reason, having a schema with that property causes problems. Currently, that property is not presented in the table, and it is overwritten (although no changes are done to the database, only the visible data is changed).
_objectKey
This is a reserved property name for Realm-specific unique object identification. Currently, any property with that name would be overwritten.
Solution
It would be enough to wrap every object in another object in the following manner:
{realObject: {
...
},_objectKey: ...,}
This would fix the problem with overwriting the _objectKey property.
Further research should be done about what happens when a schema has this field - would it overwrite the object._objectKey() method? Would RealmJS allow that?
The problem with key property could potentially be solved be making it a special case when declaring column objects for and tables.
The text was updated successfully, but these errors were encountered:
The problem
key
and_objectKey
are fields, which have a special meaning for this project.key
It is a field, that has to be set to every row in antd table as its unique identifier. For that reason, having a schema with that property causes problems. Currently, that property is not presented in the table, and it is overwritten (although no changes are done to the database, only the visible data is changed).
_objectKey
This is a reserved property name for Realm-specific unique object identification. Currently, any property with that name would be overwritten.
Solution
It would be enough to wrap every object in another object in the following manner:
This would fix the problem with overwriting the
_objectKey
property.Further research should be done about what happens when a schema has this field - would it overwrite the
object._objectKey()
method? Would RealmJS allow that?The problem with
key
property could potentially be solved be making it a special case when declaring column objects for and tables.The text was updated successfully, but these errors were encountered: