Skip to content

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

Closed
wants to merge 3 commits into from
Closed

Fixed some typos and syntax errors in the Twig reference #4469

wants to merge 3 commits into from

Conversation

javiereguiluz
Copy link
Member

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.
Copy link
Member

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 _ ?

Copy link
Member

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>`.
Copy link
Member

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.

@wouterj
Copy link
Member

wouterj commented Nov 16, 2014

How does this work together with #4432 ? Are there some conflicts?

@xabbuh
Copy link
Member

xabbuh commented Nov 16, 2014

I don't think so. But we could merge one first and rebase the other one to ensure that nothing goes wrong.

@wouterj
Copy link
Member

wouterj commented Nov 20, 2014

@javiereguiluz could you please rebase?

@javiereguiluz
Copy link
Member Author

@wouterj I don't know how to do it because I deleted my forked repo, that's why this PR shows unknown repository as the branch name. Should I create a new PR?

@xabbuh
Copy link
Member

xabbuh commented Nov 21, 2014

@javiereguiluz What you can do is basically (assumed that this repo is your local upstream repository):

$ 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.

@javiereguiluz
Copy link
Member Author

@xabbuh I'm afraid that I destroyed everything: local repo, fork on GitHub, everything!

I'll do a new PR.

@stof
Copy link
Member

stof commented Nov 21, 2014

@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)

@javiereguiluz
Copy link
Member Author

Closed in favor of #4954

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