Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Code style standardization on form type options#4967

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
Closed
Show file tree
Hide file tree
Changes fromall commits
Commits
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
2 changes: 1 addition & 1 deletionreference/forms/types/collection.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -327,7 +327,7 @@ well as :ref:`cookbook-form-collections-new-prototype`.
prototype_name
~~~~~~~~~~~~~~

**type**: ``String`` **default**: ``__name__``
**type**: ``string`` **default**: ``__name__``

If you have several collections in your form, or worse, nested collections
you may want to change the placeholder so that unrelated placeholders are
Expand Down
2 changes: 1 addition & 1 deletionreference/forms/types/entity.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -183,7 +183,7 @@ directly.
choices
~~~~~~~

**type**: array | ``\Traversable`` **default**: ``null``
**type**:``array`` | ``\Traversable`` **default**: ``null``

Instead of allowing the `class`_ and `query_builder`_ options to fetch the
entities to include for you, you can pass the ``choices`` option directly.
Expand Down
2 changes: 1 addition & 1 deletionreference/forms/types/options/attr.rst.inc
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
attr
~~~~

**type**: array **default**:Emptyarray
**type**:``array`` **default**:``array()``

If you want to add extra attributes to an HTML field representation
you can use the ``attr`` option. It's an associative array with HTML attributes
Expand Down
2 changes: 1 addition & 1 deletionreference/forms/types/options/button_attr.rst.inc
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
attr
~~~~

**type**: array **default**:Emptyarray
**type**:``array`` **default**:``array()``

If you want to add extra attributes to the HTML representation of the button,
you can use ``attr`` option. It's an associative array with HTML attribute
Expand Down
2 changes: 1 addition & 1 deletionreference/forms/types/options/constraints.rst.inc
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
constraints
~~~~~~~~~~~

**type**: array or :class:`Symfony\\Component\\Validator\\Constraint` **default**: ``null``
**type**:``array`` or :class:`Symfony\\Component\\Validator\\Constraint` **default**: ``null``

Allows you to attach one or more validation constraints to a specific field.
For more information, see :ref:`Adding Validation<form-option-constraints>`.
Expand Down
2 changes: 1 addition & 1 deletionreference/forms/types/options/error_mapping.rst.inc
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -4,7 +4,7 @@ error_mapping
.. versionadded:: 2.1
The ``error_mapping`` option was introduced in Symfony 2.1.

**type**: ``array`` **default**: ``empty``
**type**: ``array`` **default**: ``array()``

This option allows you to modify the target of a validation error.

Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp