Amend null processing for NGSI-LD #1118
Conversation
If an NGSI-LD value is sent with a null attribute, remove it from the NGSI-LD payload.
|
Related to FIWARE/context.Orion-LD#919 For Orion-LD and the following workaround: "value": {
"@type": "Intangible",
"@value": null
}It is causing inconsistency between brokers. So it looks like this phrase will be tightened up, so the existing resolved to a
I suggested to @Neeraj-Nec and @naveennec that a PR could be raised to deal with this. The fix is simple - if an NGSI-LD attribute value is parsed as |
| const context = { | ||
| op: 'IoTAgentNGSI.Entities-LD' | ||
| }; | ||
| const NGSIv2 = require('./entities-NGSI-v2'); |
There was a problem hiding this comment.
Please add an entry in CHANGES_NEXT_RELEASE file about the fix/change done in this PR.
| "prettier --parser markdown --tab-width 4 --print-width 120 --write --prose-wrap always", | ||
| "git add" | ||
| "prettier --parser markdown --tab-width 4 --print-width 120 --write --prose-wrap always" | ||
| ], | ||
| "*.js": [ | ||
| "prettier --config .prettierrc.json --write", | ||
| "git add" | ||
| "prettier --config .prettierrc.json --write" |
There was a problem hiding this comment.
Could you elaborate in this change, please?
There was a problem hiding this comment.
Since lint-staged@10.0.0 you can omit git add in the config - see https://github.com/okonet/lint-staged#v10
From v10.0.0 onwards any new modifications to originally staged files will be automatically added to the commit. If your task previously contained a git add step, please remove this. The automatic behaviour ensures there are less race-conditions, since trying to run multiple git operations at the same time usually results in an error.
There was a problem hiding this comment.
Thanks for the clarification. NTC
2 participants
If an NGSI-LD value is sent with a null attribute, remove it from the NGSI-LD payload.