Skip to content

Improve wording regarding type safety for entity fields #8339

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
markstory merged 1 commit into from
Sep 24, 2026
Merged

Improve wording regarding type safety for entity fields #8339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/en/orm/entities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,8 +176,8 @@ $article->hasValue('links'); // false
### Declaring Concrete Properties

In CakePHP 6.0 entity fields can be mapped onto real class properties instead
of being stored only as dynamic fields. This lets you use native PHP types in
your entities while continuing to use CakePHP's entity features such as
of being stored only as dynamic fields. This gives you type safety for
your entity fields while continuing to use CakePHP's entity features such as
`get()`, `set()`, `patch()`, dirty tracking, original values, and mass
assignment.

Expand Down
Loading