Make event section descriptions consistent in Readme.md #302
Conversation
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
* Some descriptions were after the code, some were before. Now they are all before the code sample they pertain to. * `field` has no description, `fileBegin` had `field`'s description, `file` had `fileBegin` and `file`'s descrition. Now they are all in the proper section.
|
Also, this is all in reference to the |
|
Yea... I'm always confused too. Closing this, I'll update the docs soon. #414 |
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 a non-code PR, but the documentation was bugging me a little.
fieldhas no description,fileBeginhadfield's description,filehadfileBeginandfile's descrition. Now they are all in the proper section.