In Sylius 1.11, after creating a new Campaign
entity using the maker bundle, I get this error when trying to fetch a campaign using its repository:
Cannot autowire service "AppRepositoryCampaignRepository": argument "$class" of method "DoctrineORMEntityRepository::__construct()" references class "DoctrineORMMappingClassMetadata" but no such service exists.
This seems to be the code that trigger the error:
<?php
namespace AppController;
use AppRepositoryCampaignRepository;
class CampaignController extends AbstractController {
protected CampaignRepository $repository;
public function __construct(CampaignRepository $repository) {
$this->repository = $repository;
}
public function details(string $id)
{
$campaign = $this->repository->find($id);
dd($campaign);
}
}
The AppRepositoryCampaignRepository
exists and is defined as follow, which is what the Sylius documentation recommends:
<?php
namespace AppRepository;
use AppEntityCampaign;
use DoctrineBundleDoctrineBundleRepositoryServiceEntityRepository;
use SyliusBundleResourceBundleDoctrineORMEntityRepository;
/**
* @extends ServiceEntityRepository<Campaign>
*
* @method Campaign|null find($id, $lockMode = null, $lockVersion = null)
* @method Campaign|null findOneBy(array $criteria, array $orderBy = null)
* @method Campaign[] findAll()
* @method Campaign[] findBy(array $criteria, array $orderBy = null, $limit = null, $offset = null)
*/
class CampaignRepository extends EntityRepository
{
}
How to fix this error?
3
Answers
TL;DR
It turns out Sylius is quite picky on both the type hinting and the variable name. This is due to how Symfony's dependency injection works and how Sylius chose to use it.
Change the constructor to:
How are you supposed to guess that?
You need to use the
bin/console debug:container
command. But if you try, you'll run into the same error message as when running you controller action.What you need to do is:
AppControllerCampaignController::__construct()
method)bin/console debug:container CampaignRepository
This will return you a list of services:
SyliusComponentResourceRepositoryRepositoryInterface $campaignRepository
but any of the suggestions with a parameter name should work)If you're curious how this works, have a look here: https://symfony.com/doc/current/service_container/autowiring.html#dealing-with-multiple-implementations-of-the-same-type
As a type-hint you can use any of the interfaces that the repository class implements, the base ones that can be used for any resource repository are
SyliusComponentResourceRepositoryRepositoryInterface
andDoctrinePersistenceObjectRepository
. For built-in Sylius resources, there are repository interfaces in the lower-level components and sometimes in the core component, likeSyliusComponentOrderRepositoryOrderRepositoryInterface
andSyliusComponentCoreRepositoryOrderRepositoryInterface
.Plugins usually also define interfaces.
For custom repositories in your projects, you should also define interfaces if you add custom methods.
The argument name also matters.
To check which type-hints are available, together with the argument name use the command
bin/console debug:autowiring campaing
.you can add to the file services.yaml
your sercvice here -> the path of your file: autowire: true
or add the arguments manually
your sercvice here -> the path of your file: arguments:[....]