Graham Esau e151d21d6d v0.6.1

Fix a compile error that can occur when deriving `JsonSchema` from a project that doesn't reference serde_json

2019-12-09 21:25:37 +00:00

Changelog

[0.6.1] - 2019-12-09

Fix a compile error that can occur when deriving JsonSchema from a project that doesn't reference serde_json

When deriving JsonSchema, the schema's title and description are now set from #[doc] comments (https://github.com/GREsau/schemars/issues/7)
When deriving JsonSchema on structs using a #[serde(default)] attribute, the schema's properties will now include default, unless the default value is skipped by the field's skip_serializing_if function (https://github.com/GREsau/schemars/issues/6)

When the option_nullable setting is enabled (e.g. for openapi 3), schemas for Option<T> will no longer inline T's schema when it should be referenceable.

Implemented JsonSchema for more standard library types (https://github.com/GREsau/schemars/issues/3)

Unsigned integer types (usize, u8 etc.) now have their minimum explicitly set to zero
Made prepositions/conjunctions in generated schema names lowercase
- e.g. schema name for Result<MyStruct, Vec<String>> has changed from "Result_Of_MyStruct_Or_Array_Of_String" to "Result_of_MyStruct_or_Array_of_String"
Some provided JsonSchema implementations with the same type but different formats (e.g. i8 and usize) used the type as their name. They have now been updated to use format as their name.
- Previously, schema generation would incorrectly assume types such as MyStruct<i8> and MyStruct<usize> were identical, and give them a single schema definition called MyStruct_for_Integer despite the fact they should have different schemas. Now they will each have their own schema (MyStruct_for_i8 and MyStruct_for_usize respectively).