Skip to content

Split deprecated-statement rule into multiple rules #1578

@bhirsz

Description

@bhirsz

Currently deprecated-statement covers different deprecations (but not all of them). It's not consistent and requires special handling to cover support for different versions (as specific statements may be deprecated in different versions) and is not supported with existing --target-version option. For that reason we should split it into multiple rules.

For example:

  • deprecated-force-tags
  • deprecated-run-keyword-if
  • deprecated-run-keyword-unless
  • deprecated-loop-keyword -> not sure if we should use 1 rule, or split for various statements like Continue For Loop, Continue For Loop If etc
  • deprecated-return -> same, as we have [RETURN] and Return From Keyword. We may have separate rules

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions