Repository navigation
Conversation
…pi-platform#8613) The Client class check added in api-platform#8574 ran first and autoloaded Client, which uses HttpClientTrait. Without symfony/http-client that is a fatal error, and the trait check that used to cover it was never reached. Fixes api-platform#8612 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ionNormalizer (api-platform#7890) Co-authored-by: soyuka <soyuka@users.noreply.github.com>
…adataCollectionFactoryTest prophesize
|
Thanks for the PR this looks like a new feature, I need to check what the consequences are on the openapi / hydra specs. Can you target main ? |
I figured it was a bugfix, as Im not adding a new functionality to the framework, and am changing the incorrect parameter type in the generated spec to the correct type. But I can ofcourse target main if preferred 👍 |
…pi-platform#8613) The Client class check added in api-platform#8574 ran first and autoloaded Client, which uses HttpClientTrait. Without symfony/http-client that is a fatal error, and the trait check that used to cover it was never reached. Fixes api-platform#8612 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ionNormalizer (api-platform#7890) Co-authored-by: soyuka <soyuka@users.noreply.github.com>
…adataCollectionFactoryTest prophesize
…' into link-uri-variable-schema-inference
The correct answer is :no I can't ... |
When defining URI variables using
Linkwithout an explicitschema, OpenAPI generated path parameters defaulted to generic string types and lost format information (such as UUID/ULID or integer types) from the target property metadata.This PR infers primitive schema
typeandformatinLinkFactoryfrom the linked property when none is explicitly configured on theLink.Functional Test
tests/Functional/OpenApiLinkSchemaTest.php