8000 [Validator] Uuid constraint reference by colinodell · Pull Request #3619 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

[Validator] Uuid constraint reference #3619

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.

Sign up for GitHub

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 3 commits into from
Mar 26, 2014
Merged

[Validator] Uuid constraint reference #3619

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f4afaab
Documentation for the new Uuid constraint
colinodell Feb 28, 2014
3ea9137
List the UUID constraint in the reference section
colinodell Feb 28, 2014
6f6c03f
Fix formatting issues
colinodell Feb 28, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fix formatting issues
  • Loading branch information
@colinodell
colinodell committed Feb 28, 2014
commit 6f6c03fe6c28994909f7eafebbaaa46f1de07fa2
15 changes: 7 additions & 8 deletions reference/constraints/Uuid.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
Uuid
==
====

.. versionadded:: 2.5
The Uuid constraint was added in Symfony 2.5.
The Uuid constraint was introduced in Symfony 2.5.

Validates that a value is a valid `Universally unique identifier (UUID)`_ per `RFC 4122`_.
By default, this will validate the format according to the RFC's guidelines, but this can
Expand Down Expand Up @@ -97,12 +97,12 @@ strict
**type**: ``boolean`` **default**: ``true``

If this option is set to ``true`` the constraint will check if the UUID is formatted per the
RFC's input format rules: ``216fff40-98d9-11e3-a5e2-0800200c9a66``. Setting this to ``false``
will allow alternate input formats like::
RFC's input format rules: ``216fff40-98d9-11e3-a5e2-0800200c9a66``. Setting this to ``false``
will allow alternate input formats like:

216f-ff40-98d9-11e3-a5e2-0800-200c-9a66
{216fff40-98d9-11e3-a5e2-0800200c9a66}
216fff4098d911e3a5e20800200c9a66
* ``216f-ff40-98d9-11e3-a5e2-0800-200c-9a66``
* ``{216fff40-98d9-11e3-a5e2-0800200c9a66}``
* ``216fff4098d911e3a5e20800200c9a66``

versions
~~~~~~~~
Expand All @@ -123,4 +123,3 @@ All five versions are allowed by default.
.. _`Universally unique identifier (UUID)`: http://en.wikipedia.org/wiki/Universally_unique_identifier
.. _`RFC 4122`: http://tools.ietf.org/html/rfc4122
.. _`UUID versions`: http://en.wikipedia.org/wiki/Universally_unique_identifier#Variants_and_versions

0