python-desert

> Or, maybe it can just go away? Yeah

Polyfield looks interesting. I think it'd be worthwhile to make sure we're not duplicating ideas that may have already been well worked out in, say, [marshmallow-jsonschema](https://github.com/fuhrysteve/marshmallow-jsonschema).

> OpenAPI 3.0 uses an extended subset of JSON Schema Specification Wright Draft 00 (aka Draft 5) to describe the data formats. “Extended subset” means that some keywords are supported...

Where's the indication that 1 is a float? Do we only want that if the defining schema has a union field for "green" (which it presumably doesn't here)?

If we are assuming the loader's schema is the same as the dumpers, and key ordering is canonicalized or maintained, there could be a `List[int]` as a top-level value where...

Hey @obi1kenobi, welcome! That Serde link gives a great rundown of our options. @altendky's polyfield link above looks like what Serde calls "adjacently tagged", and marshmallow-union looks like the "untagged"...

@altendky > Are the specific strings "type", "t", and "c" significant? I'm guessing they come from the `#[serde(tag = "t", content = "c")]` declaration just above the enum.

@altendky > Side note, should we talk more about marshalling to Python dict/list/int/float/str/bool/None rather than serializing to JSON object/array/number/true/false/null? I think that's what we're doing already, since `schema.dump(obj)` returns a...

@altendky > 2) whether to tag even when there isn't any ambiguity. Edit: moved this idea into [a new issue](https://github.com/python-desert/desert/issues/93).

Will it be easiest for us to use polyfield as a dependency to get this feature or should we do it independently?