Skip to content

Commit 8bc589a

Browse files
committed
docs: decorate db column names
1 parent 3800c5d commit 8bc589a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

user_guide_src/source/models/entities.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,9 +144,9 @@ As an example, imagine you have the simplified User Entity that is used througho
144144
.. literalinclude:: entities/008.php
145145

146146
Your boss comes to you and says that no one uses usernames anymore, so you're switching to just use emails for login.
147-
But they do want to personalize the application a bit, so they want you to change the name field to represent a user's
147+
But they do want to personalize the application a bit, so they want you to change the ``name`` field to represent a user's
148148
full name now, not their username like it does currently. To keep things tidy and ensure things continue making sense
149-
in the database you whip up a migration to rename the `name` field to `full_name` for clarity.
149+
in the database you whip up a migration to rename the ``name`` field to ``full_name`` for clarity.
150150

151151
Ignoring how contrived this example is, we now have two choices on how to fix the User class. We could modify the class
152152
property from ``$name`` to ``$full_name``, but that would require changes throughout the application. Instead, we can

0 commit comments

Comments
 (0)