`path-segment-plural` built in rule

Is your feature request related to a problem? Please describe.

Path items are often named in the plural: /customers.

Describe the solution you’d like

lint:
  rules:
     path-segment-plural: error

Path items are often named in the plural: /customers.

This should ignore path parameters and take the segment prior if the path parameter is there… example:

Path items: /customers/{customerId}… the rule should identify there is a path parameter and remove the /{customerId} from that before evaluating if it is plural (ends in an s).

Describe alternatives you’ve considered

It is similar to #394. It could be path-includes-pattern?

Additional context none

[RomanHotsiy]

Yes, I feel like this is still a valid use-case way to often, e.g.

• https://stripe.com/docs/api/invoices/pay
• https://api-reference.rebilly.com/tag/Invoices#operation/PostInvoiceAbandonment

While it could be refactored to PUT /invoice-abandonments or PUT invoice-payments I believe it would make API worse.

This is a completely different discussion though not related to the rule itself.

@andriyl making sure you see the updates here ^.

[adamaltman]

That’s very good. (Although that example is still a violation in my view… this happens with command-like APIs which are generally avoided.)