Repository navigation
Generate the fallback specification with swagger-php's Builder - #88
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When no specification is given or found, the Laravel and Slim adapters generate one from source. That used
Generator, which swagger-php 7 deprecates, and ended in anErrorwhen swagger-php is not installed.The generation moves into a protected
generateOpenApiSpecification(). It usesBuilderwhere available,Generatorbefore swagger-php 6.4, and otherwise throws aLogicExceptionnaming the files looked for and the package to install.The mode is left at swagger-php's default. Forcing hybrid would switch 6.x output from 3.0.0 to 3.1.0 and change how
nullableis verified. A project written inOpenApi\Specattributes on 6.x can override the method withMode::SPEC.