Can't use custom API components after upgrading to fumadocs-openapi@5.0.3

[0sssama]

1. I've just upgraded to fumadocs-openapi@5.0.3 and I'm unable to use some custom API components that I've built, such as my own APIPlayground component, the new APIPage component introduced by the new package version doesn't seem to allow for this.

2. As a side issue, my OpenAPI configuration is split into multiple files, this doesn't seem to be a case handled by the new createOpenAPI method from fumadocs-openapi. Passing a directory instead of a single OpenAPI yaml file results in the following error. Am I doing something wrong?

[fuma-nama]

1. You can still access the default components from fumadocs-openapi/ui, and override certain components with the renderer option of createOpenAPI.

2. Because we omitted the OpenAPI Schema path/url on generated MDX pages, createOpenAPI requires an OpenAPI Schema but doesn't support multiple schemas. I think opening a feature request for this would be more appropriate.