daniel.moran
daniel.moran
Is there any way to know what operations are currently supported under which interface? E.g.: Are de Discovery operations supported? Or the WriteAttributes operation? I've been testing my implementation of...
A `sonar-project.properties` file is needed in order to extract metrics for the repository. It should be filled following the example of other of our Node.js projects: ``` https://github.com/telefonicaid/fiware-pep-steelskin/blob/master/sonar-project.properties ```
I'm not sure why this file ended up in the folder root, but it seems to be part of an IDE files or something similar. It should be removed and,...
Current command execution features make the Context Provider calls to command attributes trigger "Execute" calls in the client successfully, but the IoTAgent is not correctly changing the Command status and...
Some decisions were taken concerning OMA Registry mapping that may be subjected to further discussion: - All the attributes are registered as passive. - The resource name in the DDF...
There are currently some differences between both objects, mainly concerning the LWM2M Mappings.
The IoT Agent currently gives support for OMA Registry object types, and the resources defined specifically for those types in their DDFs. For the third party objects, a list of...
Currently, the IoT Agent does not check COAP query parameters have supported characters, and this cause late errors unconnected with the user input. Add an early check in the user...
There are some refactors that seem urgent to me: the `sth_database.js` file is currently 1466 lines long. I'm absolutely sure it can be splitted into smaller functionally meaningful units
Multiple unit tests where defined in the Mocha script, but just one of them was implemented. This gap should be filled.