Skip to content

✏ Fix typo in docs/tutorial/relationship-attributes/define-relationships-attributes.md #239

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
tiangolo merged 2 commits into from
Aug 27, 2022
Merged

✏ Fix typo in docs/tutorial/relationship-attributes/define-relationships-attributes.md #239

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
457caf6
Fix typo in relationship-attributes tutorial
jalvaradosegura Feb 8, 2022
03ee522
Merge branch 'main' into fix/typo-in-tutorial
tiangolo Aug 27, 2022
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
2 changes: 1 addition & 1 deletion docs/tutorial/relationship-attributes/define-relationships-attributes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ Next, use that `Relationship` to declare a new attribute in the model classes:

## What Are These Relationship Attributes

This new attributes are not the same as fields, they **don't represent a column** directly in the database, and their value is not a singular value like an integer. Their value is the actual **entire object** that is related.
These new attributes are not the same as fields, they **don't represent a column** directly in the database, and their value is not a singular value like an integer. Their value is the actual **entire object** that is related.

So, in the case of a `Hero` instance, if you call `hero.team`, you will get the entire `Team` instance object that this hero belongs to. ✨

Expand Down