Adam Leventhal

It seems like it might be viable to have `#[serde(default)]` for an `enum` that implements `Default`. I could imagine this being challenging for an externally tagged enum since the type...

It would be useful to support integer values e.g. for `maximum` that are larger than can be accurately represented by an `f64`. `schemars` could even support an optional dependency on...

Fix handling of attributes applied to unit variant types

1

Fixes #151 Attributes applied to unit variants are not obeyed. In particular this was evident with `doc` and `deprecated` attributes which were simply ignored.

Here's the rust type checked by the `deprecated_enum` test: ```rust #[derive(JsonSchema)] #[deprecated] enum DeprecatedEnum { Unit, #[deprecated] DeprecatedUnitVariant, #[deprecated] DeprecatedStructVariant { foo: i32, #[deprecated] deprecated_field: bool, }, } ``` And...

non-Serialize defaults are silently ignored

2

The fix for #115 made it so that the `#[serde(default)]` annotation doesn't generate a build error when the type of the field to which the annotation is applied is not...

tag JSON schema for common Rust types with an extension

4

I'm building a couple of crates that involve turning JSON Schema into Rust types via either a build.rs or a macro. I'm finding that it would be useful to be...

With `#[serde(untagged)]`, variant names to not appear in the JSON Schema. It seems reasonable to include that data in the metadata.

support extension attribute

2

It would be useful to be able to annotate a container with something like `#[schemars(extension = "x-foo-bar")]` and have those values appear in SchemaObject::extensions. I'd be happy to submit a...

Quotes around font-family in scss files makes svgs susceptible to line-wrap corruption

1

**Is your feature request related to a problem? Please describe.** When used from https://github.com/asciidoctor/asciidoctor-diagram svgs generated by github.com/mermaid-js/mermaid-cli are line-wrapped which causes them to be corrupted. While clearly asciidoctor-diagram should...

Too many API Gateway endpoints can quickly run you into the Cloud Formation limit of 200 resources. AWS docs suggest using a nested CF stacks: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html