Enhancements and Alignments in Errors#329
Merged
rartych merged 6 commits intocamaraproject:mainfrom Dec 3, 2024
Merged
Conversation
2 tasks
…o Enhancements_and_Alignments_in_Errors
2 tasks
rartych
reviewed
Nov 25, 2024
rartych
reviewed
Nov 25, 2024
Co-authored-by: Rafal Artych <121048129+rartych@users.noreply.github.com>
Contributor
Author
|
Working on this, i will advise you @rartych, @patrice-conil |
Contributor
Author
|
Please, you can check: latest commit 9365440 Hope have considered suitably your comments Rafal:
|
Contributor
Author
|
NOTE: Pending to review and align section 6.1. Please do not review yet |
Contributor
Author
|
02/DIC: Ready for Review |
6 tasks
This was referenced Dec 16, 2024
1 task
8 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
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 is to address agreements within #321
statusto be documented in API Spec YAMLWhich issue(s) this PR fixes:
Fixes #321
Does this PR introduce a breaking change?
Changes in error codes to be used in API defintions
Special notes for reviewers:
Ready for review
Changelog input
Additional documentation
N/A