Magento 2.1 – Source Class Generation Does Not Exist Error in setup:di:compile

magento-2.1

I have added a Repository interface in my Api directory and it's implementation in located under Models directory.

I have setup the preference for the interface in etc/di.xml.

When I run bin/magento setup:di:compile the following error is thrown in the console.

Source class "\Namespace\Module\Model\PostInterface" for
"Namespace\Module\Model\PostRepository" generation does not exist.

I have no idea why the system is searching for "\Namespace\Module\Model\PostInterface" while I have mentioned clearly the location of the implementation class in di.xml.

Any suggestions are welcome with thanks !!

More Info:

When I remove the Repository implementation file i.e;
app/code/Namespace/Module/Model/PostRepository.php (imlpements
app/code/Namespace/Module/Api/PostRepositoryInterface.php), the error
disappears.

Also, when I rename the file from
app/code/Namespace/Module/Model/PostRepository.php to
app/code/Namespace/Module/Model/PostRepositoryy.php, the error
disappears.

Is there any conventions that needs to be followed while using Repositories ?

Best Answer

After a lot of Code analysis and Google searches, I found the fix for this problem. Adding the following to the di.xml fixed this issue.

<type name="Magento\Framework\Model\Entity\RepositoryFactory">
        <arguments>
            <argument name="entities" xsi:type="array">
                <item name="Namespace\Module\Api\Data\PostInterface" xsi:type="string">Namespace\Module\Api\Data\PostRepositoryInterface
                </item>
            </argument>
        </arguments>
    </type>

Related Solutions

Magento 2 – Source Class Result for ResultFactory Generation Does Not Exist

Add use Magento\Framework\Controller\ResultFactory; after namespace line. You have missing Above class file.

<?php

namespace Neo\Pincode\Controller\Index;

use Magento\Framework\Controller\ResultFactory;

class Index extends \Magento\Framework\App\Action\Action
{
    protected $_logger;

    protected $_responseFactory;

    protected $_messageManager;

    protected $_scopeConfig;

    protected $_urlInterface;

    public function __construct(
        \Magento\Framework\App\Action\Context $context,// Context injection
        \Magento\Framework\App\Config\ScopeConfigInterface $scopeConfig, // ScopeConfig injection
        \Psr\Log\LoggerInterface $logger //log injection
    ) {
        $this->_resultFactory = $context->getResultFactory();
        $this->_scopeConfig = $scopeConfig;
        $this->_logger = $logger;
        $this->_messageManager = $context->getMessageManager();
        parent::__construct($context);
    }

    public function execute()
    {
        $isValid = 0;
        $availablePincodes =  $this->_scopeConfig->getValue('pincode_section/pincode_group/pincode_field', \Magento\Store\Model\ScopeInterface::SCOPE_STORE);
        $pincodes = explode(",",$availablePincodes);
        $userPincode = $this->getRequest()->getParam('pincode');
        foreach ($pincodes as $key => $value) {
            if($value==$userPincode){
                $isValid==1;
                break;
            }
        }
        if($isValid==1){
            $this->_messageManager->addSuccess("Delivery available for above area");
        }
        else{
            $this->_messageManager->addError("Delivery not available for above area");
        }

        $resultRedirect = $this->_resultFactory->create(ResultFactory::TYPE_REDIRECT);
        $resultRedirect->setUrl($this->getBaseUrl().'checkout/cart');
        return $resultRedirect;  
    }
}

remove var folder and clear cache. Check again.

Magento 2.1 Shipping – Fix ReflectionException: Class Does Not Exist

I my case,

I had actually a syntax error in the constructor. but it was not shown as usual errors with line number. I ran,

php bin/magento setup:di:compile

It displayed there is a syntax error and showed line number. Then updgrade,

php bin/magento setup:upgrade

and deploy,

php bin/magento setup:static-content:deploy

for developer mode,

php bin/magento setup:static-content:deploy -f

It may be helpful.

Related Topic