Skip to content

Fixed the explanation of the utf8 router option #12636

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
Nov 23, 2019

Conversation

javiereguiluz
Copy link
Member

No description provided.

When this option is set to ``true``, route patterns can include UTF-8 characters.
When this option is set to ``true``, the regular expressions used in the
:ref:`requirements of route parameters <routing-requirements>` will match any
UTF-8 character when using ``.``, instead of matching only a single byte.
Copy link
Member

Choose a reason for hiding this comment

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

The u modifier influences a bit more than just the ., doesn't it? IIRC it also changes how the \w class matches for example.

wouterj added a commit that referenced this pull request Nov 23, 2019
…guiluz)

This PR was merged into the 4.3 branch.

Discussion
----------

Fixed the explanation of the utf8 router option

Commits
-------

6884e4d Fixed the explanation of the utf8 router option
wouterj added a commit that referenced this pull request Nov 23, 2019
wouterj added a commit that referenced this pull request Nov 23, 2019
* 4.3:
  [#12636] Link to PHP.net's UTF-8 docs
  Fixed the explanation of the utf8 router option
wouterj added a commit that referenced this pull request Nov 23, 2019
* 4.4:
  [#12636] Link to PHP.net's UTF-8 docs
  Fixed the explanation of the utf8 router option
@wouterj wouterj merged commit 6884e4d into symfony:4.3 Nov 23, 2019
@wouterj
Copy link
Member

wouterj commented Nov 23, 2019

Thank Javier!

I've updated this slightly in 4bf63bb, to make the explanation a bit broader + link to PHP.net's documentation the u modifier.

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.

5 participants