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

Commit07bc4db

Browse files
committed
use "Form component" instead of "form framework"
1 parentbd5ca26 commit07bc4db

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

‎book/forms.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1867,7 +1867,7 @@ an array.
18671867

18681868
Be advised, however, that in most cases using the ``getData()`` method is
18691869
a better choice, since it returns the data (usually an object) after
1870-
it's been transformed by theform framework.
1870+
it's been transformed by theForm component.
18711871

18721872
Adding Validation
18731873
~~~~~~~~~~~~~~~~~

‎book/translation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -573,7 +573,7 @@ the framework:
573573
Translating Constraint Messages
574574
-------------------------------
575575

576-
If you're using validation constraints with theform framework, then translating
576+
If you're using validation constraints with theForm component, then translating
577577
the error messages is easy: simply create a translation resource for the
578578
``validators``:ref:`domain<using-message-domains>`.
579579

‎cookbook/form/data_transformers.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,8 +169,8 @@ when creating your form. Later, you'll learn how you could create a custom
169169

170170
Cool, you're done! Your user will be able to enter an issue number into the
171171
text field and it will be transformed back into an Issue object. This means
172-
that, after a successful submission, the Formframework will pass a real Issue
173-
object to ``Task::setIssue()`` instead of the issue number.
172+
that, after a successful submission, the Formcomponent will pass a real
173+
``Issue``object to ``Task::setIssue()`` instead of the issue number.
174174

175175
If the issue isn't found, a form error will be created for that field and
176176
its error message can be controlled with the ``invalid_message`` field option.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp