Skip to content

Commit 0103d21

Browse files
authored
Trim whitespace
1 parent 670b87a commit 0103d21

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/tutorial/relationship-attributes/type-annotation-strings.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ In the first Relationship attribute, we declare it with `List["Hero"]`, putting
1616

1717
///
1818

19-
What's that about? Can't we just write it normally as `List[Hero]`?
19+
What's that about? Can't we just write it normally as `List[Hero]`?
2020

2121
By that point, in that line in the code, the Python interpreter **doesn't know of any class `Hero`**, and if we put it just there, it would try to find it unsuccessfully, and then fail. 😭
2222

@@ -26,7 +26,7 @@ But by putting it in quotes, in a string, the interpreter sees it as just a stri
2626

2727
But the editor and other tools can see that **the string is actually a type annotation inside**, and provide all the autocompletion, type checks, etc. 🎉
2828

29-
And of course, **SQLModel** can also understand it in the string correctly. ✨
29+
And of course, **SQLModel** can also understand it in the string correctly. ✨
3030

3131
That is actually part of Python, it's the current official solution to handle it.
3232

0 commit comments

Comments
 (0)