Skip to content
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

Fix typo and readability #786

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix typo and readability #786

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/source/schema-evolution.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ For example, suppose we had a `msgspec.Struct` type representing a user:

.. code-block:: python

>>> import msgpsec
>>> import msgspec

>>> from typing import Set, Optional

Expand All @@ -48,7 +48,7 @@ accomplish this, we add ``phone`` as an _optional_ field (defaulting to
... email: Optional[str] = None
... phone : Optional[str] = None

Messages serialized using the new and old schemas can still be exchanged
Messages serialized using both the old and new schemas can still be exchanged
without error. If an old message is deserialized using the new schema, the
missing fields all have default values that will be used. Likewise, if a new
message is deserialized with the old schema the unknown new fields will be
Expand Down