api-platform.com

问题 While attempting to install Api-Platform (or run composer update on an existing Api-Platform installation, I get an error like this: Uncaught Error: Argument 1 passed to ApiPlatform\Core\Bridge\Doctrine\Orm\Metadata\Property\DoctrineOrmPropertyMetadataFactory::__construct() must be an instance of Doctrine\Common\Persistence\ManagerRegistry, instance of Doctrine\Bundle\DoctrineBundle\Registry given, called in App_KernelDevDebugContainer.php on line 1530 ["exception" => TypeError { …}] What can

问题 I have a versioned Symfony API instance that I want to configure in the following manner: api.com/api/v1 -> /srv/api-v1/public/index.php api.com/api/v2 -> /srv/api-v2/public/index.php I've tried to approach this using nginx location and aliases, as it's Symfony we use try_files (as recommended) to check for an actual file prior to defaulting to index.php . Problem It seems there is a known nginx bug that breaks the $uri variable with an alias and try_files . How can I get around this bug to

问题 I have a versioned Symfony API instance that I want to configure in the following manner: api.com/api/v1 -> /srv/api-v1/public/index.php api.com/api/v2 -> /srv/api-v2/public/index.php I've tried to approach this using nginx location and aliases, as it's Symfony we use try_files (as recommended) to check for an actual file prior to defaulting to index.php . Problem It seems there is a known nginx bug that breaks the $uri variable with an alias and try_files . How can I get around this bug to

问题 In the GET operations, I'd like to exclude from the returning collections my entities that have an " archive" field that equals " true ". I'd like that to be the default for my endpoints like /users or /companies and i want to avoid to add an URL filter by hand like /users?filter[archive]=true what would be the best way to do that ? Thanks for any help :) 回答1: I had to do something like that, and I solved it by applying a DoctrineExtension to a Collection that will add the WHERE clause to the

问题 In the GET operations, I'd like to exclude from the returning collections my entities that have an " archive" field that equals " true ". I'd like that to be the default for my endpoints like /users or /companies and i want to avoid to add an URL filter by hand like /users?filter[archive]=true what would be the best way to do that ? Thanks for any help :) 回答1: I had to do something like that, and I solved it by applying a DoctrineExtension to a Collection that will add the WHERE clause to the

问题 I've been looking for a solution for a while but none of the one I find really allows me to do what I want. I would just like to create routes that don't necessarily require an entity or id to be used. Can you help me the documentation is not clear to do this. Thank you beforehand. 回答1: Thanks you for answer. I had some information but not everything. I will try the weekend. 回答2: As you can read in the General Design Considerations, just make an ordinary PHP class (POPO). Give it an

问题 I'm working with Symfony5 and ApiPlatform with phpunit for the tests I'm running tests on field validation. My issue comes from the fact that I want to restrain the user's possiblity to enter a blank string in a property named name as follow : /** * @ApiResource( * attributes={ * "normalization_context"={"groups"={"cons:read", "cons:list"}}, * "denormalization_context"={"groups"={"cons:write"}} * }, * collectionOperations={ * "get"={ * "mehtod"="GET", * "normalization_context"={"groups"={

问题 I'm working with Symfony5 and ApiPlatform with phpunit for the tests I'm running tests on field validation. My issue comes from the fact that I want to restrain the user's possiblity to enter a blank string in a property named name as follow : /** * @ApiResource( * attributes={ * "normalization_context"={"groups"={"cons:read", "cons:list"}}, * "denormalization_context"={"groups"={"cons:write"}} * }, * collectionOperations={ * "get"={ * "mehtod"="GET", * "normalization_context"={"groups"={

问题 I'm working with Symfony5 and ApiPlatform with phpunit for the tests I'm running tests on field validation. My issue comes from the fact that I want to restrain the user's possiblity to enter a blank string in a property named name as follow : /** * @ApiResource( * attributes={ * "normalization_context"={"groups"={"cons:read", "cons:list"}}, * "denormalization_context"={"groups"={"cons:write"}} * }, * collectionOperations={ * "get"={ * "mehtod"="GET", * "normalization_context"={"groups"={

来源： https://stackoverflow.com/questions/63131826/repository-in-pre-write-event-returns-query-data-not-saved-data