telefonicaid / telefonicaid/iotagent-node-lib
Add entitTypeExp (for use with ngsiv2 payloads to allow define entityType as measure_type
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
We need a similar mechanism to:
"entityNameExp": "measure_id"
but for entityType, maybe defining entityTypeExp
and then allow use:
"entityNameExp": "measure_id"
Related tests example:
In this example there is a ngsiv2 measure with several entities:
https://github.com/telefonicaid/iotagent-json/blob/1c6d13005f7c18ccedb8d99f8dbcf5515ea19e97/test/un…
And this is the payload sent to CB
https://github.com/telefonicaid/iotagent-json/blob/1c6d13005f7c18ccedb8d99f8dbcf5515ea19e97/test/un…
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 with the ngsiv2 measure-reporting handling for the existing entityNameExp option, then review test/unit/ngsiv2/HTTP_receive_ngsiv2_measures-test.js and contextRequests/ngsiv2PayloadMultipleMeasure.json. Add coverage for configuring the entity type from a measure field, and consider the work done when the generated NGSIv2 entities use that value and the related tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100