-
Notifications
You must be signed in to change notification settings - Fork 91
Add NGSI-LD multi-measures support #847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add NGSI-LD multi-measures support #847
Conversation
- split NGSI-v1, NGSI-v2 and NGSI-LD into separate files - Move common REST functions into restUtils.js - ensure that ids are URNS (adding urn:ngsi-ld: where necessary) - Use Batch Upsert endpoint throughout ( `/ngsi-ld/v1/entityOperations/upsert/`) instead of PATCH update - Update test expectations - Split NGSI v2 and NGSI-LD registrations
- Update CNR - Add Docker ENV to docs - basic LD set-up documentation - amend copy-paste JavaDoc - add missing JavaDoc - remove blank lines.
Merge branch 'feature/time-and-geo' into feature/ngsi-ld-multimeasure
…ngsi-ld-multimeasure
|
PR #843 has been merged and base branch changed to feature/842_ngsi_ld in this PR. So I understand you should upgrade jason-fox:feature/ngsi-ld-multimeasure with telefonicaid:feature/842_ngsi_ld |
| ); | ||
| } | ||
|
|
||
| //console.error(JSON.stringify(options.json, null, 4)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leftover comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but - the multiple instances of console.error (commented out) are being used to help generate the responses for the tests.
When the final PR is processed I'll remove them all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noted in the accumulative PR - #849 (comment)
NTC with regards this PR
|
I think the PR is ok (except for a couple of very minor comments easy to fix) However, regarding:
I like the refactor to move separate parts into -NGSI-LD.js -NGSI-v1.js and- NGSI-v2.js files in different parts. However, I wonder about the usual question: which impact could have this change into other existing PRs? Could you analyze it a little bit and provide feedback, pls? |
Co-Authored-By: Fermín Galán Márquez <[email protected]>
This is very simple - All of the split Going forward, reducing the file size means that it is even less likely that a clash will occur - besides which it is practically impossible to read a single 2000+ line file with interleaving implementations of three near duplicates of each function with only fractional differences between them. [sigh] It also allows for:
|
|
Note that things like #835 can touch files like |
fgalan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. The rationale is sound :)
LGTM
/ngsi-ld/v1/entityOperations/upsert/) instead of PATCH update