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
It would be nice to be able to enable a transformer or another from within the file.
For instance, let's say my robotidy configuration files states that SmartSortKeywords transformer is disabled.
SmartSortKeywords
Then maybe for some files I actually want to activate it.
I am using VSCode format on save, rather than manually running robotidy now and then, or from the CI.
It would be convenient that I can activate a transformer using a comment, like it is possible for robocop rules. # robocop: on=rule1
# robocop: on=rule1
For our example here, something like:
# robotidy: enable=SmartSortKeywords (on is as good as enable as far as I can tell).
# robotidy: enable=SmartSortKeywords
on
enable
Which could be added at the beging of the file, or in the *** Keywords *** section.
*** Keywords ***
The text was updated successfully, but these errors were encountered:
bhirsz
No branches or pull requests
It would be nice to be able to enable a transformer or another from within the file.
For instance, let's say my robotidy configuration files states that
SmartSortKeywords
transformer is disabled.Then maybe for some files I actually want to activate it.
I am using VSCode format on save, rather than manually running robotidy now and then, or from the CI.
It would be convenient that I can activate a transformer using a comment, like it is possible for robocop rules.
# robocop: on=rule1
For our example here, something like:
# robotidy: enable=SmartSortKeywords
(on
is as good asenable
as far as I can tell).Which could be added at the beging of the file, or in the
*** Keywords ***
section.The text was updated successfully, but these errors were encountered: