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
Describe the bug
Realm Studio is unable to deal with fields that have { type: "set", objectType: "objectId" }. They are incorrectly labeled as having an 'objectID' type within Realm Studio, but I have verified using realm-js that it is a Realm.Set and I am able to use .add(), .delete(), and can print the set items with .every(). It also crashes Realm Studio if I click on the column header.
To Reproduce
Steps to reproduce the behavior:
Create schema with a property that is a set of objectIds.
Open the realm in Realm Studio
Expected behavior
I expect to be able to see all the objectIds I have stored within the set. It works with UUID, but not objectId.
Screenshots
Versions:
OS: Windows 11 Version 10.0.22000 Build 22000
Studio Version 12.0.0
Additional context
None
The text was updated successfully, but these errors were encountered:
@blaykelarue Thank you for reporting. I believe you are right. Studio's support for sets is not great, unfortunately. I can't give a timeline for when we will add it to Studio.
for sure, thanks for the update nonetheless! i can work around it, unfortunately this is for a nodejs application, but i'll keep that plugin in mind for the future!
Describe the bug
Realm Studio is unable to deal with fields that have { type: "set", objectType: "objectId" }. They are incorrectly labeled as having an 'objectID' type within Realm Studio, but I have verified using realm-js that it is a Realm.Set and I am able to use .add(), .delete(), and can print the set items with .every(). It also crashes Realm Studio if I click on the column header.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to be able to see all the objectIds I have stored within the set. It works with UUID, but not objectId.
Screenshots
Versions:
Additional context
None
The text was updated successfully, but these errors were encountered: