Feature | Extend Swagger Coverage for controller OAuth2SummitScheduleSettingsApiController

[matiasperrone-exo]

Task:

Ref: https://app.clickup.com/t/86b6wkh7d

[caseylocker]

@matiasperrone-exo only one issue with the namespace.

Wrong Namespace in Security Schema
File: app/Swagger/Security/SummitScheduleSettingsAuthSchema.php
namespace App\Swagger\Security; // WRONG
Should be:
namespace App\Swagger\schemas; // CORRECT

While you're in there is there any reason that you're using numerical responses missed with constants in responses? E.g.
responses: [
new OA\Response(response: 204, description: 'No Content'), // <- Why?
new OA\Response(response: Response::HTTP_UNAUTHORIZED, description: "Unauthorized"),

We should stick with one or the other.

[matiasperrone-exo]

Thanks @caseylocker for the comments, is now ready for review.

[caseylocker]

Looks good. @smarcet if you agree please merge.

[smarcet]

@matiasperrone please re review the openapi doc generation is failing and there are some confiicts

[caseylocker]

@matiasperrone-exo the issue looks like it's in SummitSchemas.php. The schema parameter in OA\Property expects a string (schema name reference), not an OA\Schema object.
Remove the unnecessary wrapper OA\Property with the nested schema: parameter and define the properties directly on the SummitScheduleConfig schema

[smarcet]

LGTM