Closed patilsnr closed 10 months ago
What issue does this address, and why is the new way better than the old one?
Why $version is not a field? where is the $version for reported?
The Json should be something like:
{
"properties" : {
"desired" : {
"myProp" : "myValue",
"$version" : 3
},
"reported" : {
"myProp" : "myValue",
"$version" : 4
}
}
}
What issue does this address, and why is the new way better than the old one?
My understanding is that this is consistent with what the V1 API returns. Without this fix an extra level of serialization exists where "key" and "value" are literally written into the json object
/azp run
/azp run
What issue does this address, and why is the new way better than the old one?
My understanding is that this is consistent with what the V1 API returns. Without this fix an extra level of serialization exists where "key" and "value" are literally written into the json object
What is returned by IoT Hub?
What issue does this address, and why is the new way better than the old one?
My understanding is that this is consistent with what the V1 API returns. Without this fix an extra level of serialization exists where "key" and "value" are literally written into the json object
What is returned by IoT Hub?
Running a quick test with a device in my own Hub, I get:
{\"properties\":{\"desired\":{\"$version\":1},\"reported\":{\"$version\":1}}}
which looks more in line with the desired format. @rido-min could you please verify?
/azp run
TwinProperties.ToJson()
will now return something like this: