Draft
Conversation
rimi-itk
force-pushed
the
feature/application-metadata
branch
from
bfc6002 to
f6ade8b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds application metadata. See OS2iot/OS2iot-frontend#220 for the matching frontend.
The metadata is essentially the same as used on IoT Devices with one major difference: The application metadata is stored as a JSON object (with string keys and values) in a JSON field.
Metadata for devices is stored in a JSON field as well, but the actual value is a string containing a JSON encoded object, e.g.
"{\\"name\\":\\"Mikkel\\"}".