Remove "TBD" comment about extensions#162
Merged
Merged
Conversation
We don't need the TBD since each mapping/serialization doc we produce should state how extensions should appear. E.g. cloudevents#148 Closes: cloudevents#125 Signed-off-by: Doug Davis <dug@us.ibm.com>
Contributor
|
LGTM |
Collaborator
Author
|
I consider this more of a clean-up/syntax thing for the spec. If we can get some more reviews on this before the meeting then we can resolve it quickly. thanks |
markito
approved these changes
Apr 19, 2018
Collaborator
Author
|
Approved on 4/19 call |
clemensv
pushed a commit
to clemensv/spec
that referenced
this pull request
May 16, 2018
We don't need the TBD since each mapping/serialization doc we produce should state how extensions should appear. E.g. cloudevents#148 Closes: cloudevents#125 Signed-off-by: Doug Davis <dug@us.ibm.com>
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
3 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.
We don't need the TBD since each mapping/serialization doc we produce
should state how extensions should appear. E.g. #148
Closes: #125
Signed-off-by: Doug Davis dug@us.ibm.com