fix: allow description and other fields to be override seperately

[ceesvanegmond]

Q	A
Branch?	main
Tickets	Closes #7405 (added functionality)
License	MIT
Doc PR

This PR adds functionality to override the description and other fields from YAML. Previously, this was possible using annotations, but currently, it's not possible to override only the description. While it is possible to override the response HTTP status, doing so replaces the entire key. With this change, you can now override just the description field.

[soyuka]

can you target 4.2?

[ceesvanegmond]

@soyuka 👍

[VincentLanglet]

This seems fine to me and just require test

[VincentLanglet]

And I wonder if the same is required for XMLExtractor

[ceesvanegmond]

@VincentLanglet I will add tests and also fix this for XMLExtractor

EDIT: XMLExtractor already works https://github.com/ceesvanegmond/core/blob/fix/override-description-in-yaml-operation/src/Metadata/Extractor/XmlResourceExtractor.php#L205

[VincentLanglet]

EDIT: XMLExtractor already works ceesvanegmond/core@fix/override-description-in-yaml-operation/src/Metadata/Extractor/XmlResourceExtractor.php#L205

It creates an array while it would be better to instanciate a Route object

[ceesvanegmond]

@VincentLanglet I guess you mean new Response(). Just added it for XML.
Cannot get phpunit locally to work (this component phpunit setup) so have to look into that a little bit later.

[soyuka]

Note that with Symfony deprecating the xml configuration less and less people are going to use that.

[soyuka]

thanks!