Specification release candidate #243
Open
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
…to issue/233_Strongly_typed_collections_in_API_documentation
asbjornu
approved these changes
Aug 29, 2022
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.
This is an initial pull request of a possible release candidate of the specification. It is a derivative of the PR #240 and is still missing solution for the issue #241, yet it has been moved to the pure markdown document compatible with bikeshed tool that generates and index.html file.
It is mostly the document that was created by the community last years with several improvements, reorganized paragraphs, updated diagram and some fixes. It also contains baked list of introduced members with all the examples for scenarios I could think of.
Feel free to deliberate about the document!