You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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: .+\/$ ?
The text was updated successfully, but these errors were encountered:
When I have a path that is a single slash (
/
) I get this rule throwing an error.Detailed description
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
isnotEndsWith: /
, but maybe it should be something likenotMatch: .+\/$
?The text was updated successfully, but these errors were encountered: