-
Notifications
You must be signed in to change notification settings - Fork 15
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
Introduce response status errors #176
Introduce response status errors #176
Conversation
Signed-off-by: Leonard Lyubich <[email protected]>
Signed-off-by: Leonard Lyubich <[email protected]>
Signed-off-by: Leonard Lyubich <[email protected]>
…ilures Signed-off-by: Leonard Lyubich <[email protected]>
29c2009
to
4e9864b
Compare
…e sections Signed-off-by: Leonard Lyubich <[email protected]>
4e9864b
to
d9f1225
Compare
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.
I think it is time to merge it finally.
cc7af00
to
c3e3080
Compare
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.
Looks good in spec pdf
Can you, please, clarify to me (not in code) how to interpret such common comments:
|
Signed-off-by: Leonard Lyubich <[email protected]>
c3e3080
to
e636b7e
Compare
@carpawell, common scheme is:
Сommon failures are special: they apply equally to all operations. It is inconvenient to copy them in manual mode, and there is no autogeneration, at least not yet. Therefore, the description of the codes of this section should be found in the place of their definition. |
Related #150.
Docs will be added right after structural finalization.