Skip to content

consistent spelling #4671

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 16 commits into from
May 22, 2015
Merged

consistent spelling #4671

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
5b8e84d
consistency, replace "e-mail" with "email"
xabbuh Jul 20, 2014
83238aa
consisteny, use "front-end" instead of "frontend" or "front end"
xabbuh Jul 20, 2014
85fb0b1
consistency, replace "save-handler" with "save handler"
xabbuh Jul 20, 2014
7eb1847
unify "Symfony Standard Edition" usages
xabbuh Dec 19, 2014
b2d802e
use "stylesheet" instead of "Stylesheet"
xabbuh Dec 19, 2014
1bd33ca
"web debug toolbar" instead of "Web Debug Toolbar"
xabbuh Dec 19, 2014
f8db4b0
use "object-oriented" instead of "object oriented"
xabbuh Dec 20, 2014
fd52cd3
use boolean instead of Boolean
Dec 22, 2014
9c02eda
unify EventDispatcher/event dispatcher usages
xabbuh Dec 22, 2014
95c842c
use "console command" instead of "Console Command"
xabbuh Dec 23, 2014
b774651
unify event subscriber usages
xabbuh Dec 23, 2014
5b6895a
unify exception usages
xabbuh Dec 23, 2014
bd5ca26
use "full-stack" instead of "full stack"
xabbuh Dec 29, 2014
07bc4db
use "Form component" instead of "form framework"
xabbuh Dec 29, 2014
6b7d536
use "Symfony Framework" instead of "Symfony framework"
xabbuh Dec 29, 2014
f182121
uppercase "dependency injection"
xabbuh Dec 29, 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
Next Next commit
use "Form component" instead of "form framework"
  • Loading branch information
@xabbuh
xabbuh committed May 1, 2015
commit 07bc4db2c6a960b8c46840fbce99f6e1421f6159
2 changes: 1 addition & 1 deletion book/forms.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1867,7 +1867,7 @@ an array.

Be advised, however, that in most cases using the ``getData()`` method is
a better choice, since it returns the data (usually an object) after
it's been transformed by the form framework.
it's been transformed by the Form component.

Adding Validation
~~~~~~~~~~~~~~~~~
Expand Down
2 changes: 1 addition & 1 deletion book/translation.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -573,7 +573,7 @@ the framework:
Translating Constraint Messages
-------------------------------

If you're using validation constraints with the form framework, then translating
If you're using validation constraints with the Form component, then translating
the error messages is easy: simply create a translation resource for the
``validators`` :ref:`domain <using-message-domains>`.

Expand Down
4 changes: 2 additions & 2 deletions cookbook/form/data_transformers.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,8 +169,8 @@ when creating your form. Later, you'll learn how you could create a custom

Cool, you're done! Your user will be able to enter an issue number into the
text field and it will be transformed back into an Issue object. This means
that, after a successful submission, the Form framework will pass a real Issue
object to ``Task::setIssue()`` instead of the issue number.
that, after a successful submission, the Form component will pass a real
``Issue`` object to ``Task::setIssue()`` instead of the issue number.

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