We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure that each guideline defined in
Has an example .sql file. Which will be used by the genmodel to include it in rules.xml for SonarQube.
For Hint rules bad/good examples should be defined. For TrivadisPlsqlNaming rules a link to the Naming Convetions chapter of the Trivadis PL/SQL & SQL Guidelines should be enough.
The text was updated successfully, but these errors were encountered:
PhilippSalvisberg
Successfully merging a pull request may close this issue.
Ensure that each guideline defined in
Has an example .sql file. Which will be used by the genmodel to include it in rules.xml for SonarQube.
For Hint rules bad/good examples should be defined.
For TrivadisPlsqlNaming rules a link to the Naming Convetions chapter of the Trivadis PL/SQL & SQL Guidelines should be enough.
The text was updated successfully, but these errors were encountered: