当前位置：文江博客话题详情

无法覆盖 Symfony2 GeneratorBundle 中的标准骨架视图

发布于 2024-12-02 00:38:05 字数 266 浏览 1 评论 0原文

我无法覆盖 GeneratorBundle 的骨架视图。

我首先尝试在 /app/Resources/SensioGeneratorBundle/sculpt/crud/views/index.html.twig 中添加我的视图，

但它不起作用，所以我尝试创建一个扩展 SensioGeneratorBundle 的新捆绑包，并将我的视图复制到其中资源文件夹。

我已经设法使用树枝形式的主题，但我需要个性化由doctrine:generate:crud 命令生成的视图。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

清眉祭 2024-12-09 00:38:05

首先：相应的骨架视图位于此处：

vendor/bundles/Sensio/Bundle/GeneratorBundle/Resources/skeleton/crud

快速而肮脏，您应该可以通过覆盖这些视图文件来解决问题 - 但这不是我们想要的；）

在：

vendor/bundles/Sensio/Bundle/GeneratorBundle/Command/GenerateDoctrineCrudCommand.php

有一个生成器的访问器：

protected function getGenerator()
{
    if (null === $this->generator) {
        $this->generator = new DoctrineCrudGenerator($this->getContainer()->get('filesystem'), __DIR__.'/../Resources/skeleton/crud');
    }

    return $this->generator;
}

可以尝试覆盖此方法在您的扩展 Bundle 中并在构造函数中设置不同的 $sculptureDir 。

编辑：

在我的测试环境中如何实现它的快速示例（我只做了一个快速测试；）：

为自定义生成器生成一个新的包：php app/consolegenerate:bundle< /code> 并按照说明进行操作。不需要路线。我为此示例选择：Acme/CrudGeneratorBundle（或使用现有的包）

在新创建的包目录中创建一个名为“Command”的文件夹。

将命令类放置在此文件夹中。

<?php
//src/Acme/CrudGeneratorBundle/Command/MyDoctrineCrudCommand.php

namespace Acme\CrudGeneratorBundle\Command;

use Sensio\Bundle\GeneratorBundle\Generator\DoctrineCrudGenerator;

class MyDoctrineCrudCommand extends \Sensio\Bundle\GeneratorBundle\Command\GenerateDoctrineCrudCommand
{
    protected function configure()
    {
        parent::configure();
        $this->setName('mydoctrine:generate:crud');
    }

    protected function getGenerator()
    {
        $generator = new DoctrineCrudGenerator($this->getContainer()->get('filesystem'), __DIR__.'/../Resources/skeleton/crud');
        $this->setGenerator($generator);
        return parent::getGenerator();
    }
}

将vendor/bundles/Sensio/Bundle/GeneratorBundle/Resources/sculpture/crud复制到您的资源中（在我的示例中为“src/Acme/CrudGeneratorBundle/Resources/crud”）

First of all: The corresponding skeleton views are located here:

vendor/bundles/Sensio/Bundle/GeneratorBundle/Resources/skeleton/crud

Quick and dirty you should be fine by overriding these view files - but thats not what we want ;)

In:

vendor/bundles/Sensio/Bundle/GeneratorBundle/Command/GenerateDoctrineCrudCommand.php

there is an accessor for the Generator:

protected function getGenerator()
{
    if (null === $this->generator) {
        $this->generator = new DoctrineCrudGenerator($this->getContainer()->get('filesystem'), __DIR__.'/../Resources/skeleton/crud');
    }

    return $this->generator;
}

One can try to override this method in your extending Bundle and set a different $skeletonDir in the constructor.

Edit:

Quick example in my test environment how it can be achieved (I only made a quick test ;):

Generate a new bundle for the custom generator: php app/console generate:bundle and follow the instructions. A route is not needed. I chose for this example: Acme/CrudGeneratorBundle (Or use an existing bundle)

Create a folder called "Command" in the newly created bundle directory.

Place a command class in this folder.

<?php
//src/Acme/CrudGeneratorBundle/Command/MyDoctrineCrudCommand.php

namespace Acme\CrudGeneratorBundle\Command;

use Sensio\Bundle\GeneratorBundle\Generator\DoctrineCrudGenerator;

class MyDoctrineCrudCommand extends \Sensio\Bundle\GeneratorBundle\Command\GenerateDoctrineCrudCommand
{
    protected function configure()
    {
        parent::configure();
        $this->setName('mydoctrine:generate:crud');
    }

    protected function getGenerator()
    {
        $generator = new DoctrineCrudGenerator($this->getContainer()->get('filesystem'), __DIR__.'/../Resources/skeleton/crud');
        $this->setGenerator($generator);
        return parent::getGenerator();
    }
}

Copy the vendor/bundles/Sensio/Bundle/GeneratorBundle/Resources/skeleton/crud to your Resources (in my example "src/Acme/CrudGeneratorBundle/Resources/crud")

回复收藏 0 原文