-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
📝 Change the word "unwrap" to "unpack" in docs/en/docs/tutorial/extra-models.md
#13061
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.
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
📝 Change the word "unwrap" to "unpack" in docs/en/docs/tutorial/extra-models.md
#13061
Conversation
While 'unwrap' (or 'unwrapping') is a Pydantic-specific convention, its usage in the documentation might lead to confusion. The document mentions 'unwrap' with the prefix 'Python', which could incorrectly imply that 'unwrap' is official Python terminology. The behavior of 'unwrap' described in the tutorial/extra-models document aligns with the "dictionary unpacking" feature in Python dictionary displays (https://docs.python.org/3/reference/expressions.html#dictionary-displays). Therefore, if the intended behavior is indeed Python's dictionary unpacking, I suggest replacing 'unwrap' with 'unpack' for clarity and consistency with official Python terminology.
📝 Docs preview for commit e25c443 at: https://0748e877.fastapitiangolo.pages.dev Modified Pages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable.
다음과 같이 번역하였습니다. - unwrap -> 언랩(unwrap) fastapi#13061 의 accept 여부에 따라 번역 변경 예정 - unwraping -> 언래핑(unwrapping) fastapi#13061 의 accept 여부에 따라 번역 변경 예정 - type annotation -> 타입주석(type annotation) - argument value -> 인자 값(argument value)
다음과 같이 번역하였습니다. - unwrap -> 언랩(unwrap) fastapi#13061 의 accept 여부에 따라 번역 변경 예정 - unwraping -> 언래핑(unwrapping) fastapi#13061 의 accept 여부에 따라 번역 변경 예정 - type annotation -> 타입주석(type annotation) - argument value -> 인자 값(argument value)
📝 Docs preview for commit 0c35135 at: https://ce28ecff.fastapitiangolo.pages.dev Modified Pages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me!
📝 Docs preview for commit 9d977fe at: https://963b8c36.fastapitiangolo.pages.dev Modified Pages |
📝 Docs preview for commit aa6f6b2 at: https://c8fd93cf.fastapitiangolo.pages.dev Modified Pages |
📝 Docs preview for commit 9317543 at: https://c61e6ad6.fastapitiangolo.pages.dev Modified Pages |
docs/en/docs/tutorial/extra-models.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, thanks! ☕
다음과 같이 번역하였습니다. - unwrap -> 언랩(unwrap) fastapi#13061 의 accept 여부에 따라 번역 변경 예정 - unwraping -> 언래핑(unwrapping) fastapi#13061 의 accept 여부에 따라 번역 변경 예정 - type annotation -> 타입주석(type annotation) - argument value -> 인자 값(argument value)
While 'unwrap' (or 'unwrapping') is a Pydantic-specific convention, its usage in the documentation might lead to confusion. The document mentions 'unwrap' with the prefix 'Python', which could incorrectly imply that 'unwrap' is official Python terminology.
The behavior of 'unwrap' described in the tutorial/extra-models document aligns with the "dictionary unpacking" feature in Python dictionary displays (https://docs.python.org/3/reference/expressions.html#dictionary-displays).
Therefore, if the intended behavior is indeed Python's dictionary unpacking, I suggest replacing 'unwrap' with 'unpack' for clarity and consistency with official Python terminology.