Added float type cast to fix OpenAPI returned string type. #134
Conversation
This file contains 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
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.
Quick-Fix for issue #132. Inconsistent data types from Kiosk and OpenAPI, float vs string, while the common code assumed float only. A float type cast will (probably) fix this. Needs to be verified on a OpenAPI installation, only tested by me on Kiosk.
A re-factoring to a more consistent use of data types is recommended as a long term proper correction. And in that case perhaps also take care of the midnight glitches in "yearEnergy" and "monthEnergy" data sets.