telefonicaid / telefonicaid/iotagent-node-lib
Valiadation of the configuration objects
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
Currently, no validation is applied to the object passed as a configuration. See https://github.com/telefonicaid/iotagent-node-lib/blob/develop/lib/commonConfig.js#L157
This may cause problems in case the users of this module pass malformed-configurations.
Validating that the provided configuration is a valid one is needed.
This should be also implemented at a concrete agents level in case they also take configuration objects.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at lib/commonConfig.js around line 157 to understand where configuration objects enter the module and what validation is currently absent. Then inspect the concrete agents that accept configuration objects, since the issue requires validation at those levels too. Done means malformed configurations are rejected consistently, with the validation requirements and affected agent entry points covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100