Releases: nelmio/NelmioApiDocBundle
Releases · nelmio/NelmioApiDocBundle
Log model name conflicts, and fix deprecations
Merge pull request #1863 from onatskyy/fix_getCollectionValueType_dep… …recation Fix Symfony\Component\PropertyInfo\Type::getCollectionValueType() deprecation notice for symfony >=5.3
v3.9.1: Update templates comment path for bundle override (#1864)
## Changelog Fix the comment path from SwaggerUI to SwaggerUi since case does matter for template override to work.
Add compound constraints support
Merge pull request #1851 from javiereguiluz/patch-3 [Doc] Fix some minor RST issues
v4.3.0: Merge pull request #1829 from nelmio/PROPACCESS
v3.9.0
2.13.5: Merge pull request #1799 from phansys/config
Backport #1457 for 2.x
v4.2.0: Apply `enum` from Choice Constraints to Items When Choice is Multiple…
… (#1784) * Apply `enum` from Choice Constraints to Items When Choice is Multiple Otherwise JSON schema like this is generated: ``` "property": { "type": "array", "enum": ["one", "two", "three"], "items": { "type": "string" } } ``` With this change, however, this schema is generated: ``` "property": { "type": "array", "items": { "type": "string", "enum": ["one", "two", "three"] } } ``` A possible downside here is that the symfony constraint stuff happens before types are figured out from PHPDoc. So it's _possible_ to end up with something that won't validated. Take something like this: ``` /** * @Assert\Choice(multiple=true, choices={"..."}) * @var string */ ``` This would generate: ``` "property": { "type": "string", "items": { "enum": ["..."] } } ``` * Fix CS * cs * more cs * fix tests Co-authored-by: Guilhem Niot <[email protected]>