-
Notifications
You must be signed in to change notification settings - Fork 577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support optional properties #5
Comments
upon further testing, it turns out that I can't set |
That is expected for the time being. Support for optional properties was just added to the core library and needs to be extended to the js binding. In the long term all properties in js will probably be optional by default, and you will be able to indicate properties with required values in the schema definition. |
That's interesting. There is no |
In the past NULL was only supported on object/link properties. All other property types required valued to be present. This was mostly due to optimizations in the core library. Changes in core were just finished to support NULL values for all types and work is currently being done to expose this in all of the bindings. |
ok, thanks. can i keep this open until that is fixed in the JS? |
Lets keep it open. Will hopefully be working on this next week. |
some of the issues that I'm seeing could be attributed to crashing if the value is undefined.
I'm calling
realm.create(data)
let's say the table has a column named
title
but I leave it off thedata
object.I think it's crashing with "should be a string"
I was expecting it to set the value to NULL if left off.
The text was updated successfully, but these errors were encountered: