You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, There is no rule in SonarQube that restricts the number of lines of code allowed in PL/SQL files. This can lead to the creation of extensive and difficult to maintain scripts. It is important to set a limit to encourage modularity and code readability.
Suggested Solution
I request that a new rule be implemented in SonarQube that allows a maximum line of code limit to be set for PL/SQL files. This rule will help keep code within manageable parameters and promote good development practices.
Benefits
Improve readability and maintainability of PL/SQL code.
Encourage modularity and code reuse.
Facilitate the identification and correction of code problems.
Proposed Steps
Implement a new rule in SonarQube for PL/SQL that allows to define a limit of lines of code.
Allow users to configure this limit according to the needs of their projects.
Provide detailed documentation on how to use this new rule.
I hope it is a proposal that you find interesting and useful, thank you very much in advance for your work.
Best regards.
The text was updated successfully, but these errors were encountered:
Problem Description
Currently, There is no rule in SonarQube that restricts the number of lines of code allowed in PL/SQL files. This can lead to the creation of extensive and difficult to maintain scripts. It is important to set a limit to encourage modularity and code readability.
Suggested Solution
I request that a new rule be implemented in SonarQube that allows a maximum line of code limit to be set for PL/SQL files. This rule will help keep code within manageable parameters and promote good development practices.
Benefits
Proposed Steps
I hope it is a proposal that you find interesting and useful, thank you very much in advance for your work.
Best regards.
The text was updated successfully, but these errors were encountered: