Skip to content

Add clear description of resolve env processor #13417

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

Merged
merged 1 commit into from
Mar 27, 2020

Conversation

wtorsi
Copy link
Contributor

@wtorsi wtorsi commented Mar 25, 2020

Add a clear description of resolve env processor, describing what is actually resolved.

#13205

@@ -232,8 +232,8 @@ Symfony provides the following env var processors:
]);

``env(resolve:FOO)``
Replaces the string ``FOO`` by the value of a config parameter with the
same name:
Replace all matches of ``%param_name%`` in the parameter ``FOO`` by the values of a config parameters with the
Copy link
Contributor

Choose a reason for hiding this comment

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

I agree, the description here is hard to understand and your change makes it better, but I still find this a bit hard to understand, how about:

If the value of the parameter FOO contains other parameters, they will be replaced with their corresponding values.

Copy link
Member

Choose a reason for hiding this comment

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

I liked this proposal better ... but it had some issues too (e.g. FOO is not called "a parameter" in the rest of the article, etc.)

So, we reworded it as follows:

    If the content of ``FOO`` includes container parameters (with the syntax
    ``%parameter_name%``), it replaces the parameters by their values:

Add a clear description of `resolve`  env processor, describing what is actually  resolved.

symfony#13205
@javiereguiluz
Copy link
Member

@wtorsi thanks!

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.

4 participants