Refactor scan tool to retrieve rule metadata directly from Rule instance instead of rules.json #66
Description
Current Limitation
The current implementation of the Ballerina scan tool relies on a rules.json file to store and retrieve metadata such as rule IDs, descriptions, and kinds. Currently the usage of reportIssue(...) method from standard library compiler-plugins utilizes only a numeric rule ID to identify issues, with all descriptive metadata being pulled from rules.json.
Suggested Improvement
Refactor the scan tool to retrieve rule metadata directly from the passed Rule instance rather than relying on the rules.json file.
Version
No response