[FE] api-diff rules reclassification - part 1

[iugaidiana]

According to the review of asd rules, need to make the following changes:

parameters-schema & request-body-schema:

• add-required-property-with-default
  • current severity - non-breaking
  • new severity - breaking
• remove-property-compliance
  • current severity - breaking
  • new severity - non-breaking
• rename «remove-required-property» as «remove-required-status-from-property»
• new case «remove-required-property-compliance»
  • severity - breaking

response-body-schema & response-headers-schema:

• rename «remove-required-property» as «remove-required-status-from-property»
• new case «remove-required-property-compliance»
  • severity - breaking
• update-format-for-number-property
  • current severity - breaking
  • new severity - requires attention
• remove-format-for-number-property
  • current severity - breaking
  • new severity - requires attention
• decrease-minimum-for-number-property
  • current severity - breaking
  • new severity - requires attention
• decrease-minimum-for-required-number-property (new case)
  • severity - breaking
• remove-minimum-for-number-property
  • current severity - breaking
  • new severity - requires attention
• remove-minimum-for-required-number-property (new case)
  • severity - breaking
• mark-minimum-value-as-inclusive-for-number-property
  • current severity - breaking
  • new severity - requires attention
• mark-maximum-value-as-inclusive-for-number-property
  • current severity - breaking
  • new severity - requires attention
• update-multiple-of-for-number-property
  • current severity - breaking
  • new severity - requires attention
• increase-max-properties-for-object-property
  • current severity - breaking
  • new severity - requires attention
• remove-max-properties-for-object-property
  • current severity - breaking
  • new severity - requires attention
• add-non-boolean-additional-properties
  • severity - requires attention

test date for new cases - test_data.zip

[iugaidiana]

need an approval that:

• parameters-schema & request-body-schema can be classified the same
• response-body-schema & response-headers-schema can be classified the same

[iugaidiana]

@zloiadil, after implementation of ticket, it is needed to make appropriate changes in compatibility suite (also for these cases you need to set "yes" value to "Approved" column and fill out revision history.
In compatibility suite table columns "before" and "after" shall be links to test data from git repo (ask Alex for appropriate links)

[vOrigins]

reclassify add-required-property-with-default

add-required-property-with-default	send	receive
[Added] required status	non-breaking -> breaking	non-breaking

reclassify remove-property-compliance

remove-property-compliance	send	receive
[Deleted] property	breaking -> non-breaking	non-breaking

🔗 remove-all-of-option	send	receive
[Deleted] property	breaking -> non-breaking	non-breaking

🔗 remove-all-of	send	receive
[Deleted] property	breaking -> non-breaking	non-breaking

rename remove-required-property to remove-required-status-from-property

remove-required-status-from-property	send	receive
[Deleted] required status	non-breaking	breaking

new case remove-required-property-compliance

❓ Why would send be breaking? That contradicts remove-property-compliance and remove-required-status-from-property, where send is non-breaking. The cases are related, so reclassification in one affects the others.

remove-required-property-compliance	send	receive
[Deleted] required status	non-breaking	breaking
[Deleted] property	non-breaking	breaking

reclassify update-format-for-number-property

update-format-for-number-property	send	receive
[Changed] format	breaking	breaking ->requires attention

🔗 update-format-for-string-property	send	receive
[Changed] format	breaking	breaking ->requires attention

reclassify remove-format-for-number-property

remove-format-for-number-property	send	receive
[Deleted] format	non-breaking	breaking ->requires attention

🔗 remove-format-for-string-property	send	receive
[Deleted] format	non-breaking	breaking ->requires attention

reclassify decrease-minimum-for-number-property

decrease-minimum-for-number-property	send	receive
[Changed] minimum validator	non-breaking	breaking -> requires attention

new case decrease-minimum-for-required-number-property

decrease-minimum-for-required-number-property	send	receive
[Changed] minimum validator	non-breaking	breaking

reclassify remove-minimum-for-number-property

remove-minimum-for-number-property	send	receive
[Deleted] minimum validator	non-breaking	breaking -> requires attention

new case remove-minimum-for-required-number-property

remove-minimum-for-required-number-property	send	receive
[Deleted] minimum validator	non-breaking	breaking

reclassify mark-minimum-value-as-inclusive-for-number-property

mark-minimum-value-as-inclusive-for-number-property	send	receive
[Changed] exclusiveMinimum validator	non-breaking	breaking -> requires attention

reclassify mark-maximum-value-as-inclusive-for-number-property

In the same commit as mark-minimum-value-as-inclusive-for-number-property, the code is shared between exclusiveMinimum and exclusiveMaximum.

mark-maximum-value-as-inclusive-for-number-property	send	receive
[Changed] exclusiveMaximum validator	non-breaking	breaking -> requires attention

reclassify update-multiple-of-for-number-property

update-multiple-of-for-number-property	send	receive
[Changed] multipleOf validator	breaking	breaking -> requires attention

reclassify increase-max-properties-for-object-property

maxClassifier is shared across /maxLength, /maxItems, /maxProperties, and /exclusiveMaximum.

increase-max-properties-for-object-property	send	receive
[Changed] maxProperties validator	non-breaking	breaking -> requires attention

🔗 increase-max-length-for-string-property	send	receive
[Changed] maxLength validator	non-breaking	breaking -> requires attention

🔗 increase-max-items-for-array-property	send	receive
[Changed] maxItems validator	non-breaking	breaking -> requires attention

🔗 remove-sibling-maxLength-for-ref	send	receive
[Changed] maxLength validator	non-breaking	breaking -> requires attention

reclassify remove-max-properties-for-object-property

Change reverseRemove slot of maxClassifier from breaking to risky. Affects all remove cases sharing maxClassifier.

remove-max-properties-for-object-property	send	receive
[Deleted] maxProperties validator	non-breaking	breaking -> requires attention

🔗 remove-max-length-for-string-property	send	receive
[Deleted] maxLength validator	non-breaking	breaking -> requires attention

🔗 remove-max-items-for-array-property	send	receive
[Deleted] maxItems validator	non-breaking	breaking -> requires attention

reclassify add-non-boolean-additional-properties

add-non-boolean-additional-properties	send	receive
[Changed] type	breaking	non-breaking -> requires attention