Skip to content

supporting standard api version format rsther than numbers #6

Description

@AmirSasson

rather integers that represent the api version, most api versions are represented as "yyyy-mm-dd-preview" or yyyy-mm-dd.
these formats can be parsed to apiVersion which implements icomparable.
in addition why is there a limitation of only a single api version which is supported/active and all other are deprecated?

Activity

lmaysapphire commented on Nov 11, 2024

@lmaysapphire

In order to work it tags controllers/actions with every version between introduced and removed. There is no way to do this with dates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions