Eliminate 'extensions' bucket and clarifying extensibility#289
Closed
clemensv wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Clemens Vasters <clemensv@microsoft.com>
Collaborator
Contributor
Author
|
Oops. No. Sorry. I miss you already having that. I will close this one. |
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
2 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.
Dropping the extensions bucket and adding an explanation of the extensibility model.
Proof of concept code that shows an extensions bag isn't needed at the level of this specification is not needed and is rather better accommodated only in the wire-format mappings that have no support for dynamic/open schemas (ex: Thrift and Protobuf) can be found here https://github.com/clemensv/cloudeventsformatdemo