-
Notifications
You must be signed in to change notification settings - Fork 1
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
Dev/154 155 #156
Dev/154 155 #156
Conversation
google-java-format: version 1.23.0
@alexjhawk, These changes still need to be tested |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good, aside from the two recommendations. We can talk about testing tomorrow.
...com/hms_networks/americas/sc/ignition/comm/requests/m2w/M2WebEwonUpdateTagValuesRequest.java
Outdated
Show resolved
Hide resolved
...com/hms_networks/americas/sc/ignition/comm/requests/m2w/M2WebEwonUpdateTagValuesRequest.java
Outdated
Show resolved
Hide resolved
The Flexy UpdateTagForm request requires that boolean tag values are 1 or 0 and not true or false. This change updates the EwonUpdateTagValuesRequest class to convert boolean tag values to 1 or 0. Closes #155
The tag quality values differ between DataMailbox and the instant values from M2Web API. The former provides strings e.g., "good", "bad", and the later provides a bit map consisting of multiple flags. The connector maps DataMailbox responses to the instant value bitmaps. This commit corrects the mapping.
For DataMailbox responses, values are parsed to java Objects. The values 0 and 1 will be Doubles. The values True and False will be Booleans. Talk2M responses are parsed to Strings '1' and '0'. This addition will handle these possibilities.
Tag values from DataMailbox responses are parsed into Objects, which GSON makes Doubles. Tag values from Talk2M responses are parsed into Strings. This change allows for both.
@it-hms @alexjhawk are we able to get v2.0.1 merged so that we can test the Issue #154 fix? |
@alexjhawk , |
closes #154
closes #155