Setting Post `output` to `false` exception in React Admin on missing `owl:Nothing` reference

[rvanlaak]

API Platform version(s) affected: 4.2.2

Description

With output: false on a Post operation on a resource the documentation points to owl:Nothing and that leads to a failure on the React Admin documentation parsing.

How to reproduce

Set Operation output to false. In my situation the input is a DTO command and messenger is set to true.

Possible Solution

This likely relates to \ApiPlatform\Hydra\Serializer\DocumentationNormalizer::getHydraOperation based on the $outputClass, and owl:Nothing not being defined in the documentation yet.

Additional Context

[slax57]

I managed to reproduce the issue with this code.

use ApiPlatform\Metadata\Get;
use ApiPlatform\Metadata\GetCollection;
use ApiPlatform\Metadata\Post;


#[ApiResource(operations: [
    new Get(),
    new GetCollection(),
    new Post(
        output: false
    )
])]

But I can hardly see how this is related to api-platform/admin.

Here is the stacktrace of the original error:

Error: The class "http://www.w3.org/2002/07/owl#Nothing" is not defined in the API documentation.
    at findSupportedClass (parseHydraDocumentation.js:38:1)
    at findRelatedClass (parseHydraDocumentation.js:118:1)
    at fetchEntrypointAndDocs.then.Promise.reject.api._Api_js__WEBPACK_IMPORTED_MODULE_9__.Api.resources (parseHydraDocumentation.js:153:1)

And the related code:

api-doc-parser/src/hydra/parseHydraDocumentation.ts

Lines 41 to 67 in 9aa16c9

	/**
	* Finds the description of the class with the given id.
	*/
	function findSupportedClass(
	docs: ExpandedDoc[],
	classToFind: string,
	): ExpandedClass {
	const supportedClasses = get(
	docs,
	'[0]["http://www.w3.org/ns/hydra/core#supportedClass"]',
	) as ExpandedClass[] | undefined;
	if (!Array.isArray(supportedClasses)) {
	throw new Error(
	'The API documentation has no "http://www.w3.org/ns/hydra/core#supportedClass" key or its value is not an array.',
	);
	}
	for (const supportedClass of supportedClasses) {
	if (supportedClass["@id"] === classToFind) {
	return supportedClass;
	}
	}
	throw new Error(
	`The class "${classToFind}" is not defined in the API documentation.`,
	);
	}

As you can see, this either comes from the api-doc-parser code, of from the schema generated by api-platform itself.

Transferring issue to api-doc-parser for further analysis.