Conversation
Add the ability to add preferredUnits field to metadata and a unit conversion utility in server-api to convert values to preferred units in the data browser.
Remove the conversions and units that are more formatting than unit conversion.
Remove duplication in longnames - define them only ones in the units list. Improve types to be more helpful & strict.
Member
|
From a client perspective what is the pattern moving forward? |
Member
Author
|
I am thinking that stream and api contents would remain the same, for principle of least surprise and least protocol level complexity. |
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
2 participants
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.
Add the ability to add preferredUnits field to
metadata and a unit conversion utility in server-api to convert values to preferred units in the data
browser.
TODO