Parameters

Hey Alkiviadis,

Not sure I completely understand you here, but you're probably overthinking about it. First of all, in the dev env when we're changing a config file - the cache will be automatically recompiled so any new changes you made in the config will be re-parsed on the next request. In prod Symfony mode it's a bit different, when you change a config file - you will need to clear the cache manually to let the system notice your changes. So, in both cases the cache will be re-compiled and so the new parameter values will be used.

I hope this helps.

Cheers!

Thank you for your answer, but I am actually talking about the order the configurations are read, not when and if the cache is cleared.
Specifically while on (cache.yaml) we had in the middle of course:

parameters:
    cache_adapter: 'cache.adapter.filesystem'

framework:
    cache:
        app: '%cache_adapter%'

when@dev:
    parameters:
        cache_adapter: cache.adapter.array

even when we are at dev environment, framework.cache.app already got assigned a value from the first cache_adapter declaration, before the cache_adapter parameter got reassigned with new value later. But the framework.cache.app got the final value of cache_adapter, which seemed strange to me at first.

So, are all parameters parsed/set first, and then anything else?

Hey Alkiviadis,

It's important do understand that Symfony first gathers all the configuration from separate config files and only then trying to resolve parameter values. Actually, the parameter values will be resolved even later only when you fetch the service from the service container - the container will instantiate the service object and resolve all the parameter values it has.

Yeah, it probably might be confusing at first sight, but that's just an overwritten operation. Yes, when the config file is parsed - the framework.cache.app will be set to the %cache_adapter% (but it's just instructions, it's still not resolved actual value yet). And later if you're in a dev mode, the when@dev will be parsed as well which will overwrite the values that were already set before (if any).

If it's confusing you - you can avoid when@dev syntax and put the dev config inside the config/packages/dev folder, but behind the scene it will work the same anyway: it first will gather all the default config (for all environments), and only then overwrite any whiles with env-specific config.

So, even though it's an overwriting operation in some cases - that's actually really powerful and flexible: you have the default config values but can overwrite some values with other ones for specific enviroments.

I hope this clarifies things!

Cheers!

Hey Jim,

Yeah, that config/packages/ folder is special and contains bundle-specific configs :) Try to put your config in just config/ dir, it should work well this way :)

Cheers!

Thanks for the reply Victor. Unfortunately I still get the same error, also after clearing the cache. So in the config directory I have put a file app.yaml, which looks a bit like this:

app:
  foo: bar

Then when I run debug:config app I get the error described above. And when, in a console command, I have

$this->parameterBag->get('app.foo');

I get the error "You have requested a non-existent parameter "app.foo"".

Hey Jim-B,

Wait, if you drop that app.yaml file from the config/packages/ and put into config/ - you should not have that No extensions with configuration available for "app" error anymore, as nobody will parse your file at all. And this means you would need to parse that file yourself.

But in your second example I see you just want to add some data to the config so that system knows about your data. If so, you need to add "parameters" - that's how it's called in Symfony. For this, you can open config/services.yaml and under parameters: key add your data. Then you will be able to fetch those parameters with the code you showed in the end :)

Cheers!