Add --readonly-interfaces option #31
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bibermann
force-pushed
the
28-readonly-interfaces-option
branch
from
58d4c53 to
d0cb367
Compare
bibermann
force-pushed
the
28-readonly-interfaces-option
branch
from
d0cb367 to
8444eda
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #28 by providing a
--readonly-interfacesoption that prevents non-optional fields with default values to become optional in the TypeScript interface.--readonly-interfacescan be read as "create interfaces for data that is read by an API", i.e. the interface for data generated by pydantic (in contrast to data that gets deserialized by pydantic).For more information, see
README.mdas well astests/expected_results/optionals/README.md.