fix(laravel): add contact & license options to fix swagger UI issues #6802
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* feat: if a policy matches the name of a model we automatically register it, no need to do it manually anymore * fix: optimising the way we handle collection * fix: phpstan * fix: cs-fixer
* feat: add hal support for laravel * feat: quick review * fix: typo & cs-fixer * fix: typo in composer.json * fix: cs-fixer & phpstan * fix: forgot about hal item normalizer, therefore there's no more createbook nor updatebook test as Hal is a readonly format
[ci skip]
Contributor
Author
|
The failing test does not seem to be related to this change; it appears to be an existing issue on the current main branch. https://github.com/api-platform/core/actions/runs/11854768322/job/33037604217 |
Member
|
targetting 4.0 at #6804 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While using the latest version of API Platform in a Laravel application, issues arise with the Swagger UI frontend. Upon investigation, the root cause seems to be missing license and contact information in the generated OpenAPI schema.
However, these fields are not configurable via the existing configuration, requiring users to override the options singleton manually to resolve the issue.
The lack of these fields leads to the following error:
This bugfix request proposes adding support for configuring license and contact fields directly via the configuration, ensuring the Swagger UI renders without issues.
Steps to Reproduce