telefonicaid / telefonicaid/iotagent-node-lib
Corner cases provisioning `entityNameExp`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
There are 3 cases when provisioning a service group using the parameter entityNameExp
When "entityNameExp":true
{
"id": "true",
"type": "Light",
"TimeInstant": {
"type": "DateTime",
"value": "2023-04-24T16:23:55.352Z",
"metadata": {}
}
},
When "entityNameExp":false
{
"id": "Light:gps1",
"type": "Light",
"TimeInstant": {
"type": "DateTime",
"value": "2023-04-24T16:25:32.707Z",
"metadata": {}
}
},
When "entityNameExp":"patata"
{
"id": "Light:gps1",
"type": "Light",
"TimeInstant": {
"type": "DateTime",
"value": "2023-04-24T16:27:54.134Z",
"metadata": {}
}
},
When "entityNameExp":42
{
"id": "42",
"type": "Light",
"TimeInstant": {
"type": "DateTime",
"value": "2023-04-25T07:50:11.067Z",
"metadata": {}
}
},
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
The issue names no files or tests. Start by reproducing service-group provisioning with the four entityNameExp values, then trace where the parameter is handled. The expected behavior for each case is not specified, so completion requires agreeing on the intended IDs and adding coverage for them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100