Skip to content

Add new CompatibilityReference attribute #168

@PandaHugMonster

Description

@PandaHugMonster

Generally it's a bad Idea to have aliases for methods (except rare cases of very targeted shortcuts).
But when developing your code, and you need to preserve the backward-compatibility - it could be handful!

Use cases (and preserve compatibility):

  1. You need to rename a method
  2. You create a new method, but it's compatible or partially compatible with the old one
  3. You change order of arguments in a method

In all the aforementioned cases you'll have to create a new method to preserve the compatibility, and the whole or part of the functionality would migrate to this new method.

But the old method must persist as Deprecated until a certain version of your code .

-- unfinished --

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions