Skip to content
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

PartialUpdates reporting + additional improvements in error responses #4447

Merged
merged 35 commits into from
Jan 8, 2024

Conversation

fgalan
Copy link
Member

@fgalan fgalan commented Nov 17, 2023

Issue #3499

  • Fix ftest expectations
  • Manage correctly the "PartialUpdate" case
  • Specific test for this issue (check parent issue and related old PR)
    • POST /v2/op/update cases
    • Other single-entity update operations
  • Add entity type to description messages
  • Doc (if applicable)
  • CNR
  • Cleanup comments and FIXME PR marks

@@ -77,7 +79,7 @@ echo '03. PATCH /v2/entities/Room1/attrs, to update existing attribute (temperat
echo '===================================================================================================================================================================='
payload='{
"temperature": {
"value": 24,
"value": 25,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually not needed, but better to use a different value than the one in step 02.

NTC (informative)

@fgalan fgalan changed the title [WIP] PartialUpdates reporting PartialUpdates reporting + additional improvements in error responses Dec 13, 2023
@fgalan fgalan requested a review from mapedraza December 13, 2023 14:58
@@ -2816,15 +2816,25 @@ _**Request headers**_
_**Response code**_

* Successful operation uses 200 OK
* Errors use a non-2xx and (optionally) an error payload. See subsection on [Error Responses](#error-responses) for more details.
* Errors use a non-2xx code and error payload (see next subsection):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the link to the error responses section be included? (applies for each API operation)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The subsection is

_**Response payload**_

That as far as a I understand, is not link-able.

* Errors use a non-2xx and (optionally) an error payload. See subsection on [Error Responses](#error-responses) for more details.
* Errors use a non-2xx code and error payload:
* 404 Not Found for not found entity (see next subsection)
* Check addicional cases in [Error Responses](#error-responses) general documentation
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo:

Suggested change
* Check addicional cases in [Error Responses](#error-responses) general documentation
* Check additional cases in [Error Responses](#error-responses) general documentation

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed (in all places) in b46c269

@mapedraza
Copy link
Collaborator

LGTM

@mapedraza mapedraza merged commit 7b75f0b into master Jan 8, 2024
12 checks passed
@mapedraza mapedraza deleted the feature/3499_partial_updates_reporting branch January 8, 2024 14:16
@fgalan
Copy link
Member Author

fgalan commented Jan 8, 2024

@fisuda this PR does some modifications to English documentation. It would be great if you could sync the Japanese translation, please. Thanks in advance!

fisuda added a commit to fisuda/fiware-orion that referenced this pull request Jan 10, 2024
@fisuda
Copy link
Contributor

fisuda commented Jan 10, 2024

I sent the PR #4466. Thanks.

fgalan added a commit that referenced this pull request Jan 11, 2024
(JP) ADD doc about PartialUpdates reporting in error responses (#4447)
@fgalan fgalan mentioned this pull request Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants