-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat(core): align behavior for update entity attributes (1.6+ compliance) #1146
Conversation
Test Results 58 files ±0 58 suites ±0 1m 24s ⏱️ -2s Results for commit 9f62d9c. ± Comparison against base commit 3c80bbc. This pull request removes 170 and adds 30 tests. Note that renamed tests count towards both.
|
Quality Gate passedIssues Measures |
val attributePayload = expandedAttributes.getAttributeFromExpandedAttributes( | ||
ngsiLdAttribute.name, | ||
ngsiLdAttributeInstance.datasetId | ||
)!! | ||
if (currentTea != null) { |
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.
why did you place them outside the if clause ?
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.
because I need them in both clauses
logger.info(message) | ||
UpdateAttributeResult( | ||
addAttribute( | ||
entityUri, | ||
ngsiLdAttribute.name, |
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.
is this to treate the case where a temporal entity doesn't have any instances of this attribute yet ?
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.
in 1.6, new behavior states that if the attribute does not exist, it has to be added (before it had to be ignored)
No description provided.