fix(symfony): fix swagger config to support Symfony ConfigBuilders

[alexndlm]

Q	A
Branch?	3.0
Tickets	n/a
License	MIT
Doc PR	n/a

Please see https://symfony.com/doc/current/configuration.html#using-php-configbuilders and https://symfony.com/doc/current/components/config/definition.html#array-node-options

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[alexndlm]

@soyuka would you please check this PR?

[alexndlm]

@soyuka, is any chance to merge this?

[soyuka]

@vincentchalamon probably has a better idea then me of the impacts of this

[vincentchalamon]

Hi @alexndlm,

Thanks for your PR. I've tested it in an API Platform project, but can't find any difference in the generated values comparing with the actual code, both dump me the following configuration:

array:1 [
  "foo" => array:2 [
    "name" => "Authorization"
    "type" => "header"
  ]
]

Can you explain why the use of useAttributeAsKey is necessary, and if possible add a test using it, please?

[alexndlm]

@vincentchalamon, thanks that you check this PR.

I have updated the tests and rebased PR on 2.7.

This issue is only present with Symfony PHP ConfigBuilders.

Now Symfony generates the following Config Class:

My API Platform config:

And it is not possible to specify the authorization name:

With the fix in this PR, it will be the following:

[vincentchalamon]

Thanks for the clear clarification 😃
Can you add a test with ConfigBuilder to reveal the bug and fix it, please?

[alexndlm]

Done.

[vincentchalamon]

Bad commitlint (easy to fix), otherwise 👍
Good job @alexndlm!

[vincentchalamon]

Good job @alexndlm, thanks!