telefonicaid / telefonicaid/iotagent-node-lib
Proper use of supportedForwardingMode in registrations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
With the implementation of supportedForwardingMode in Orion Context Broker (issue https://github.com/telefonicaid/fiware-orion/issues/3106), the NGSIv2 registrations done by the IOTA Library should be adapted the following way:
- Registrations corresponding to lazy attributes should use
"supportedForwardingMode": "query" - Registrations corresponding to commands should use
"supportedForwardingMode": "update"
NGSIv1 and NGSI-LD will be out of the scope of this issue.
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
Locate the NGSIv2 registration-building entry points in the IOTA Library and trace how registrations for lazy attributes and commands are assembled. Verify the current registration payloads and related tests, then ensure lazy-attribute registrations use "supportedForwardingMode": "query" and command registrations use "supportedForwardingMode": "update"; NGSIv1 and NGSI-LD are out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100