Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
• Features and deprecations must be submitted against the 5.x branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

Hello @kumulo, thanks for contributing.

For the record, this kind of proposal has been rejected in the past: #32845 (comment)

I'm against having methods that allow to change the default directories. A bundle is opinionated and convention based for directories. Developers should be able to easily find things in a third party bundle, so a common directory structure is a must.

And I still agree with him, thus 👎 on my side.

On the other hand, I don't think it's so hard to achieve by implementing PrependExtensionInterface in your DI extension:

public function prepend(ContainerBuilder $container): void
{
    $container->prependExtensionConfig('twig', [
        'paths' => [
            '/<bundle_path>/custom_path/templates' => 'Custom',
        ],
    ]);

    $container->prependExtensionConfig('framework', [
        'translator' => [
            'paths' => [
                '/<bundle_path>/custom_path/translations',
            ],
        ],
    ]);
}

Hello @yceruto
Thanks, PrependExtensionInterface seems working fine ;)