-
Notifications
You must be signed in to change notification settings - Fork 1
Repo API: Property value encondings #34
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
Comments
Agreed that they should be strings, but shouldn't we say something about the format of the strings for each property type? E.g. a date property is in the ISO8601 format? |
Per #9, we only have support the default types The closest we got was something like:
meaning:
(This typedef might be shipped with LIonWeb standard library.) Some thoughts on this design include:
|
@joswarmer Are your questions answered? Then I'd close. |
Ok, I understand. You can close it. |
Possible property value encondings
Encode everything as string
Use JSON types
int
, but JSON contains42.1
int
value is > 53 bit, JSON loses precision=> Decision: for JSON transport, all primitive types are strings
Might be different for e.g. protobuf transport
The text was updated successfully, but these errors were encountered: