The rules are currently not really visible to the end user. But once we add features like // ui5lint-disable comments, // ui5lint-disable ui5-linter-no-deprecated-api seems quite redundant and inconsistent.
We initially thought a prefix would be helpful for later integration with eslint. However, eslint will prefix rules exposed by plugins with the plugin name anyways, so it would become @ui5/linter/no-deprecated-api anyways.
The rules are currently not really visible to the end user. But once we add features like
// ui5lint-disablecomments,// ui5lint-disable ui5-linter-no-deprecated-apiseems quite redundant and inconsistent.We initially thought a prefix would be helpful for later integration with eslint. However, eslint will prefix rules exposed by plugins with the plugin name anyways, so it would become
@ui5/linter/no-deprecated-apianyways.