This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
Clarification of some terms around Transaction Examples #304
Conversation
This file contains 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
| @@ -48,7 +48,7 @@ An [**HTTP Request Method**](http://en.wikipedia.org/wiki/Hypertext_Transfer_Pro | |||
|
|
|||
| <a name="def-message"></a> | |||
| ### Message | |||
| An **HTTP transaction message**. | |||
| An **HTTP ction message**. | |||
There was a problem hiding this comment.
yup, noticed immediately and fixed :)
honzajavorek
force-pushed
the
honzajavorek/clarification-of-some-terms-around-transaction-examples
branch
from
ab7249c to
617001a
Compare
| @@ -666,9 +666,9 @@ This section **may** include one nested [Attributes section][] defining the inpu | |||
|
|
|||
| Action section **should** include at least one nested [Response section](#def-response-section) and **may** include additional nested [Request](#def-request-section) and [Response](#def-response-section) sections. | |||
|
|
|||
| Nested Request and Response sections **may** be ordered into groups where each groups represent one transaction example. First transaction example group starts with the first nested Request or Response section. Subsequent groups start with the first nested Request section following a Response section. | |||
| Nested Request and Response sections **may** be ordered into implicit groups where each such group represents one transaction example. First transaction example group starts with the first nested Request or Response section. Subsequent groups start with the first nested Request section following a Response section. | |||
There was a problem hiding this comment.
"may be ordered into implicit" does not make sense. They are ALWAY forming implicit groups. That is why they are implicit 🙃
honzajavorek
deleted the
honzajavorek/clarification-of-some-terms-around-transaction-examples
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This will help me with writing of specification in apiaryio/blueprint-transactions#8 (I'll just link API Blueprint glossary and spec with all the terms).