fix(jsonSchema): Declare properties as required for Output

[VincentLanglet]

Q	A
Branch?	4.2 for bug
Tickets	Closes #7457
License	MIT
Doc PR	api-platform/docs#...

[VincentLanglet]

Looking at the implementation of OpenApiFactory, there is

$this->jsonSchemaFactory->buildSchema($resourceClass, $operationFormat, Schema::TYPE_OUTPUT, $operation, $schema, null, $forceSchemaCollection);

for the output of an api call (for instance GET)

and

$this->jsonSchemaFactory->buildSchema($resourceClass, $operationFormat, Schema::TYPE_INPUT, $operation, $schema, null, $forceSchemaCollection);

for the input of an api call PATCH/PUT/POST

Therefore I think

• We should expose in the input schema only Writable properties
• We should expose in the output schema only Readable properties (and declare them required)

It makes no sens to me to add writable property in the GET schema (or the opposite). Am i misunderstandind ?

[soyuka]

we should not expose required in my opinion as it locks the schema (for example with the PropertyFilter or GroupFilter, results can be altered).

[VincentLanglet]

Oh I understand the issue then. it's hard to document both

• call which doesn't use any propertyFilter
• and calls which are using some

[VincentLanglet]

Still it means that we shouldn't use the same schema for input and output and therefor the same cache key.

Should we start with a different cache key without changing anything?

[VincentLanglet]

Looking at the number of the test to update, I think it will be better to get your opinion on this first @soyuka
Am I misunderstanding everything or shouldn't the schema be different for the input and for the output ?