Actually, it depends on the loader implementation. The one described in this part of the documentation (YamlUserLoader code above) totally ignores thetype argument, as was done before by the DIC loaders 😅 (I think it should not appear at all in the Config component doc)

Are there plans to add this feature to these loaders too ... or it doesn't make sense? Thanks!

The only other loaders implementingLoaderInterface from the Config component are the routing ones.
They handle the$type argument quite differently:

# Symfony\Component\Routing\Loader\YamlFileLoader/** * {@inheritdoc} */publicfunctionsupports($resource,$type =null){returnis_string($resource) &&in_array(pathinfo($resource,PATHINFO_EXTENSION),array('yml','yaml'),true) && (!$type ||'yaml' ===$type);}

The type cannot be forced, but should be empty or match the extension. Maybe it can be updated to match the new behavior introduced in the di loaders.

But I still think this note should not appear in the Config component documentation, as it should described theLoaderInterface and what it is used for. It should not document implementations from other components.

👍 thanks for the explanation.

This line should be removed, right?