Skip to content

Commit 4ef26a3

Browse files
committed
Fix formatting
1 parent d8d82dd commit 4ef26a3

1 file changed

Lines changed: 10 additions & 8 deletions

File tree

en/appendices/5-3-migration-guide.rst

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -175,10 +175,8 @@ ORM
175175
- ``Table::patchEntity()``, ``Table::newEntity()``, ``Marshaller::one()`` and
176176
``Marshaller::many()`` now accept a ``strictFields`` option that only applies
177177
validation to the fields listed in the ``fields`` option.
178-
- Added ``TableContainer`` that you can register in your Application::services() to
178+
- Added ``TableContainer`` that you can register in your ``Application::services()`` to
179179
add dependency injection for your Tables.
180-
- ``Cake\ORM\Locator\TableContainer`` was added. By adding this container
181-
delegate to your application, ORM Tables can be injected by the DI container.
182180

183181
Pagination
184182
----------
@@ -231,11 +229,15 @@ Validation
231229
----------
232230

233231
- ``ipOrRange()`` validation has has been added to check for an IP or a range (subnet).
234-
- When validating within CakePHP marshalling context, the entity will be passed into the ``context`` argument for use inside custom validation rules.
235-
This can be useful when patching partially and then needing to get that data from the entity instead of the passed data.
236-
- ``existsInNullable()`` rule has been added. This rule allows ``null`` values in nullable composite foreign keys,
237-
which is semantically correct for optional relationships. Use ``$rules->existsInNullable(['author_id', 'site_id'], 'SiteAuthors')``
238-
instead of ``existsIn()`` when you want to permit null values in foreign keys.
232+
- When validating within CakePHP marshalling context, the entity will be passed
233+
into the ``context`` argument for use inside custom validation rules. This can
234+
be useful when patching partially and then needing to get that data from the
235+
entity instead of the passed data.
236+
- ``existsInNullable()`` rule has been added. This rule allows ``null`` values
237+
in nullable composite foreign keys, which is semantically correct for optional
238+
relationships. Use ``$rules->existsInNullable(['author_id', 'site_id'],
239+
'SiteAuthors')`` instead of ``existsIn()`` when you want to permit null values
240+
in foreign keys.
239241

240242
View
241243
----

0 commit comments

Comments
 (0)