-
Notifications
You must be signed in to change notification settings - Fork 25
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
Data.Value isn't an object? #121
Comments
It make sense that it should be object, but the value would have to be type checked to ensure it matches the spec. Array does not appear to be a supported value type yet.
@mamund is that correct? |
in this release of Cj, data.value is not an object. You can, however, extend Cj by adding an object property (data.object). there may already be some Cj extensions that do this, too. check out the cj extensions list and, if you don't see what you think you need, feel free to start a new extension and, as long as it is backward compatible, we can register it for others to use, too. |
Hi,
Shouldn't the Data.Value be an object, currently it's a string. In order to properly assign; int, arrays, bool, etc. you have to use the SetValue("value", true) to enforce the correct serialization. Wouldn't it be easier it the Data.Value just was an object? or I'm missing something?
Best regards
Dennis
The text was updated successfully, but these errors were encountered: