Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enum support

See original GitHub issue

Since enum support is available in api-doc-parser, an enum support could be added to InputGuesser. It will dynamically generate a SelectInput with restricted choices.

Issue Analytics

State:
Created a year ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

alanpoulaincommented, Sep 30, 2022

So you mean to implement enum SelectInput guessing despite of which dataProvider is used and only for now it will only work only for OpenAPI, without assuming that we will now have both hydra features (schemaAnalyzer) and enum guessed, am I correct?

Yes you shouldn’t know which data provider is used anyway: everything needs to be abstracted.

0reactions

PawelSuwinskicommented, Sep 30, 2022

It’s OK if we don’t have support for enum in Hydra yet. The api-doc-parser library is abstracting it anyway: you don’t need to know if Hydra or OpenAPI is used. Also this admin can be used with OpenAPI only: https://api-platform.com/docs/admin/openapi/.

So you mean to implement enum SelectInput guessing despite of which dataProvider is used and only for now it will only work only for OpenAPI, without assuming that we will now have both hydra features (schemaAnalyzer) and enum guessed, am I correct?

And if you are using API Platform 2.7, there is already an enum support for Choice constraint: https://github.com/api-platform/core/blob/8108899dc986b2c6dd4b905151a7e70229ff34d0/src/Symfony/Validator/Metadata/Property/Restriction/PropertySchemaChoiceRestriction.php#L47-L51

Nope, 2.6 from previous Api Platform Distrubution 😉, I will upgrade and check it out, thanks for pointing.