Add socket and host flags to dev server - #488
Merged
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A combined batch of framework changes.
Dev server
--socket/--host. The build-mode dev server can now bind a unix socket or an explicit host, so it can front a proxy/tunnel without owning a TCP port.Schema generation
NewTypefields before schema generation. ANewTypeidentifier carries its wire type in__supertype__; unwrap it before the instance-vs-class fallback inget_field_schema, otherwise aNewTypeinstance (not atype) falls through to__class__—typing.NewTypeitself — and the generatedpick_schemaannotation is unbuildable for pydantic.