[x] instead of treating LwM2M registry objects and custom objects seperately, at the very beginning pick all allowed registry and custom objects into on "nRF Asset Tracker LwM2M Registry" and use that
[x] remove hardcoded magic number 1563968743666, use Azure IoT Hub Metadata timestamp for the respective property. individual timestamp instead of global timestamp
[x] if importing lodash modules use the function name, not _.<functionName>. check option to use reduce and not map
[ ] question to azure: do all Azure $metadata timestamps get update when one object is changed? So we can more precisely determine update time of a single object.
[x] implement custom metadata timestamp as server time for each object
[x] rename "create..." functions/files to "convert/name"
[x] GitHub Actions should execute the example (and it should work)
[x] asset-tracker-cloud-coiote-azure-converter-js/src/index.ts at 15c5c9fe45642dcd9e41363e15f674bc7aa863e1 · MLopezJ/asset-tracker-cloud-coiote-azure-converter-js
[x] Build expected input of Asset Tracker from the result of the integration between Coiote and Azure - MLopezJ/asset-tracker-cloud-coiote-azure-converter-js
After review of code with Pisut and Markus, this is the feedback received.
any
is forbidden_.<functionName>
. check option to use reduce and not mapbeforeEach
in tests** Would be nice to add coverage badge