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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions