-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Fixed some typos and syntax errors in the Twig reference #4469
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
Conversation
javiereguiluz
commented
Nov 15, 2014
Q | A |
---|---|
Doc fix? | yes |
New docs? | no |
Applies to | all |
Fixed tickets | - |
@@ -539,7 +539,7 @@ format_file_from_text | |||
``text`` | |||
**type**: ``string`` | |||
|
|||
Uses `|format_file <format_file>` to improve the output of default PHP errors. | |||
Uses :ref:`|format_file <format_file>`_ to improve the output of default PHP errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it really need the _
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it should be ``format_file_
@@ -91,7 +91,7 @@ controller | |||
**type**: ``array`` **default**: ``[]`` | |||
|
|||
Returns an instance of ``ControllerReference`` to be used with functions like | |||
:ref:`render() <reference-twig-function-render>` and `render_esi() <render_esi>`. | |||
:ref:`render() <reference-twig-function-render>` and :ref:`render_esi() <render_esi>`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You will have to add a label before the "render_esi" headline like this:
.. _reference-twig-function-render-esi:
and then change the referenced label name here accordingly.
How does this work together with #4432 ? Are there some conflicts? |
I don't think so. But we could merge one first and rebase the other one to ensure that nothing goes wrong. |
@javiereguiluz could you please rebase? |
@wouterj I don't know how to do it because I deleted my forked repo, that's why this PR shows |
@javiereguiluz What you can do is basically (assumed that this repo is your local $ git fetch upstream +refs/pull/4469/head
$ git checkout -b <branch-name> FETCH_HEAD You can then create a new pull request based on this new branch. |
@xabbuh I'm afraid that I destroyed everything: local repo, fork on GitHub, everything! I'll do a new PR. |
@javiereguiluz you can create a new local repo without issue. Just clone the repo again. The command given by @xabbuh gets the PR content from the symfony/symfony-docs repo on github (upstream refers to the symfony repo, not your deleted fork) |
Closed in favor of #4954 |