add node listener upgrade #31
Conversation
| { | ||
| "name": "TimeInstant", | ||
| "type": "ISO8601", | ||
| "value": "2015-10-28T13:51:32+0100" |
There was a problem hiding this comment.
Is the date parsing logic strong enough to cope with miliseconds in the case the value includes it? It will work if timezone is not included?
There was a problem hiding this comment.
The miliseconds are not counted, the diff is based on seconds. It will require some tunning on how it gets the diff.
The time parser AFAIK converts all kind of formats, I have checked with this samples:
"value": "2015-10-28T13:51:32"
"value": "2015-10-28 13:51:32"
"value": "2015-10-28T13:51:32+0100"
"value": "2015-10-28T13:51:32.0011"
and even the now_time is calculated always in the same way it calculates the diff properly.
NTC
|
LGTM Not sure if I should merge (it seems that I privilegies in the iot-qa-tools repo :) or should I wait for other to do it... |
|
LGTM |
|
I've always wished to have a readme file for each one of the simulators. It's a nice to have. |
No description provided.