Skip to content

Rule path-keys-no-trailing-slash: throws lint error when path is a single slash #419

@lvl99

Description

@lvl99

When I have a path that is a single slash (/) I get this rule throwing an error.

Detailed description

paths:
  /:
    post:
      ...

I'm unsure if maybe I'm using it wrong -- I should be able to have a path at /, right?

Context

I think if it is a viable design to have an API path at / that this rule should allow for it, but still function on paths that are beyond the initial first slash.

Possible implementation

I saw in the rules that path-keys-no-trailing-slash is notEndsWith: /, but maybe it should be something like notMatch: .+\/$ ?

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