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
In relation to the upcoming RF 7.2 release, I think there's a use case for a rule to prevent the use of the new GROUP syntax. Supported by this comment from Pekka: https://robotframework.slack.com/archives/C0K0240NL/p1735646205809349?thread_ts=1735603358.090759&cid=C0K0240NL
GROUP
The text was updated successfully, but these errors were encountered:
Sure. Though I believe it should be non-default rule (disabled by default, opt-in rule).
On the topic I was already thinking about possible rules for GROUP syntax - I will open some other issues as well.
Sorry, something went wrong.
I agree on the non-default. Thanks for the effort!
No branches or pull requests
In relation to the upcoming RF 7.2 release, I think there's a use case for a rule to prevent the use of the new
GROUP
syntax.Supported by this comment from Pekka: https://robotframework.slack.com/archives/C0K0240NL/p1735646205809349?thread_ts=1735603358.090759&cid=C0K0240NL
The text was updated successfully, but these errors were encountered: