PUT new attribute backwards compatibility optional

https://github.com/OpenAPITools/openapi-diff/issues/136 made the PUT request incompatibility check stricter, considering an additional field as a breaking change. This makes sense for a scenario where updates are taking place, but is too strict if PUTs represent only inserts.

What would be the best way of optionally removing the strict handling of PUTs? Options could include:

• Surfacing more information about how the changedOperation.isIncompatible() decision was made, allowing the user of the OpenApiDiff to use more granular information to decide whether it should be considered as a breaking change.
• Adding a command-line flag to remove the PUT strictness for all cases in a run.
• Writing some code to traverse the object graph for PUTs when the diff has completed and decide whether the strict PUT handling is what caused the incompatibility, and then ignore it.

Commencez par suivre la manière dont changedOperation.isIncompatible() gère les champs ajoutés dans les requêtes PUT et la manière dont ce résultat atteint le diff terminé. Comparez les approches proposées : exposer des informations granulaires sur l’incompatibilité, ajouter une option de ligne de commande ou parcourir le graphe d’objets après le diff. Le travail est considéré comme terminé lorsqu’une seule conception est choisie et spécifiée, et que son comportement pour les PUTs en insertion uniquement et les PUTs de style mise à jour est couvert.