add documentation for rules #394
Closed
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
jesus-mg-ios
approved these changes
Oct 13, 2022
|
@MaxDesiatov do you guys accept 3rd party PRs or is this project just an internal tool and open sourced for marketing purposes? |
|
Thank you for the effort here! However, we've decided to go with the approach merged in #615, which generates the documentation automatically as part of |
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.
I pull the documentation for each rule from the rule files and aggregate them on the
Configurationpage.In the original documentation,
LintandFormatare documented as separate sections. However, here I'm putting them in the same line in the hope it will make searching for a specific rule easier. Please let me know if you prefer to break it into sub-bullets.This should solve issue #382 .