Skip to content

Use %CONFIG_DIR% in ContainerConfigurator? #236

@simshaun

Description

@simshaun

Hi,

I am organizing my backend (Symfony) and frontend (JS/SCSS/etc) files in two separate folders, with composer.json and other stuff at the root of the project. (Note: backend and frontend are only for file organization. Symfony will still be rendering most of the frontend, so it's not like its two separate apps.)

So, I've got backend/bin/, backend/config/, backend/src/, etc. I configured composer.json to set "config-dir": "backend/config". That has worked fine for installing several bundles.

However, trying to composer req validator, I get the error:

file(E:\_projects\foo/config/services.yaml): failed to open stream: No such file or directory

Looking at the ContainerConfigurator, it's using getcwd().'/config/services.yaml'.

Compare that to the BundleConfigurator which uses $this->options->expandTargetDir('%CONFIG_DIR%/bundles.php').

I think the ContainerConfigurator should also use the config-dir param. Right? I'll open a PR if so.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions