Skip to content

VersionByNamespaceConvention for major version with 2 or more digits #805

Closed
@Doomic

Description

@Doomic

We want to make a V10.0 API version and we are using VersionByNamespaceConvention configuration. But it looks like that this is not supported (if you skip the date part).
I checked the Pattern used in the VersionByNamespaceConvention and it looks like "10" is matching the second group (month). And therefore it is not seen..
It will work if we use "V___10_0" as namespace; but that will be ugly.
I would prefer an option to configure that you only use major/minor convention..
or maybe a more easy way of fixing would be; first check if it has at least 8digits before date matching will be applied.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions