Error alignments for Event Notifications Artifact#351
Merged
rartych merged 1 commit intocamaraproject:mainfrom Dec 5, 2024
Merged
Conversation
PedroDiez
requested review from
RubenBG7,
patrice-conil,
rartych and
shilpa-padgaonkar
as code owners
rartych
added a commit
to rartych/Commonalities
that referenced
this pull request
Dec 5, 2024
Fixed typos and suggestions Added camaraproject#351
11 tasks
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
This PR provides an aligment for CAMARA event notifications artifact in terms of documented errors and also API Design guidelines for mandatory errors for this artifact.
Rational is detailed in #348
Mandatory/Documented errors are proposed to be: 400, 401, 403, 410, 429. Documents impacted:
CAMARA Event Notifications artifact
API Design guidelines
Which issue(s) this PR fixes:
Fixes #348
Does this PR introduce a breaking change?
Special notes for reviewers:
Changelog input
Additional documentation
N/A