Categorize built-in rules documentation #347
Merged
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
orangain
commented
Feb 22, 2024
| Identity tables that do not have a primary key defined. Tables can be ignored by passing the `ignorePattern` rule argument. | ||
| ### require-primary-key | ||
|
|
||
| Identify tables that do not have a primary key defined. Tables can be ignored by passing the `ignorePattern` rule argument. |
There was a problem hiding this comment.
I replaced Identity with Identify. I am not sure, but I think it is a typo.
|
Very nice! |
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.
In this PR, I propose to categorize the documentation of the built-in rules into the following four categories.
Due to the increase in the number of built-in rules, this will be easier to read.
In addition, I have aligned the indentation of the codes and corrected the typo.