Skip to content

File loaders can now set the type to load explicitly #7353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from

Conversation

javiereguiluz
Copy link
Member

This fixes #7352.
I propose to document this in a subtle manner because this is rarely needed by users.
Ping @ogizanagi because he was the original author of the related PR. Thanks!

@xabbuh
Copy link
Member

xabbuh commented Jan 11, 2017

👍 for the changes, but we should document the version this feature was added to

Copy link
Contributor

@ogizanagi ogizanagi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

The changes in the dependency injection component doc look perfect as is, but I think it misses an import example, as in the original issue:

# app/config/config.yml
imports:
    - { resource: my_custom_config.ext, type: yml }

Is there any suitable place where it can be added?

.. tip::

If your application uses unconventional file extensions (for example, your
YAML files have a ``.res`` extension) you can pass the file type as the
Copy link
Contributor

@ogizanagi ogizanagi Jan 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@ogizanagi ogizanagi Jan 12, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

# Symfony\Component\Routing\Loader\YamlFileLoader
/**
 * {@inheritdoc}
 */
public function supports($resource, $type = null)
{
    return is_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 the LoaderInterface and what it is used for. It should not document implementations from other components.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 thanks for the explanation.

/*
The YamlUserLoader will be used to load this resource,
// YamlUserLoader is used to load this resource because it supports
// files with the '.yml' extension
since it supports files with a "yml" extension
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line should be removed, right?

@ogizanagi
Copy link
Contributor

Oops! Looks like I forgot something here:

Status: Reviewed

@xabbuh
Copy link
Member

xabbuh commented Feb 28, 2017

Thank you Javier.

@xabbuh xabbuh closed this in 266e14e Feb 28, 2017
@javiereguiluz javiereguiluz deleted the fix_7352 branch May 24, 2018 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FileLoaders now allow to set the type to load explicitly
6 participants