New breaking change rule: Reducing maximum values for int parameters

[savage-alex]

Please could we get a new rule added that reports when someone reduces an existing parameter maximum value down

Example of someone reducing the max value of a query parameter for pagination limits

      - name: limit
        in: query
        description: The maximum number of items to return for this call. The call also returns a token that you can specify in a subsequent call to get the next set of results.
        required: false
        style: form
        explode: true
        schema:
          maximum: 100
          minimum: 5
          type: integer
          format: int32
          default: 20
        example: 100

      - name: limit
        in: query
        description: The maximum number of items to return for this call. The call also returns a token that you can specify in a subsequent call to get the next set of results.
        required: false
        style: form
        explode: true
        schema:
          maximum: 10
          minimum: 5
          type: integer
          format: int32
          default: 20
        example: 100

[acunniffe]

Hey @savage-alex this makes sense as a rule.

I'm curious how you would like the following cases to be handled

• adding a maximum keyword when one does not currently exist.
• removing a maximum keyword entirely but keeping integer

Should we have this for minimum too? Is there a reason you did not include that or do not consider it a breaking change to raise or lower that?

[savage-alex]

Entirely an oversight on my side to not include Mins. Changing that would also break clients so should be handled. Will have a think about the various cases and drop some notes here