Skip to content
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

Issue461:Support for complex datatypes. #480

Merged
merged 4 commits into from
Apr 18, 2023
Merged

Conversation

UlfBj
Copy link
Contributor

@UlfBj UlfBj commented Apr 11, 2023

No description provided.

```
is represented by the following JSON object<br>
{"field1":"X", "field2":"Y"}<br>
where X and Y are the actual values of respective datatype, here represented for simplicity as string values.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For "plain" signals we say above that the value always shall be string values, i.e. "123", "true", "ABC" and so on. Shall it be string values here as well or should it be "native" JSON representation? I.e.:

{"my_int":123, "my_bool": true, "my_string": "my_value", "my_int_array": [10, 20, 30]}

or rather:

{"my_int":"123", "my_bool": "true", "my_string": "my_value", "my_int_array": ["10", "20", "30"]}

Maybe rephrase to make it more clear.

Would we benefit from having more examples?

@tguild tguild merged commit 825fcf0 into w3c:gh-pages Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants