Add example for remote deriving JsonSchema
This commit is contained in:
parent
b11536e527
commit
8d40625f10
5 changed files with 165 additions and 0 deletions
17
docs/examples/5-remote_derive.md
Normal file
17
docs/examples/5-remote_derive.md
Normal file
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
layout: default
|
||||
title: Derive for Remote Crate
|
||||
parent: Examples
|
||||
nav_order: 5
|
||||
summary: Deriving JsonSchema implementations for a type in somebody else's crate.
|
||||
---
|
||||
|
||||
# Deriving JsonSchema for a Type in a Different Crate
|
||||
|
||||
Rust's [orphan rule](https://doc.rust-lang.org/book/traits.html#rules-for-implementing-traits) requires that either the trait or the type for which you are implementing the trait must be defined in the same crate as the impl, so it is not possible to implement `JsonSchema` for a type in a different crate directly.
|
||||
|
||||
To work around this, Schemars provides a way of deriving `JsonSchema` implementations for types in other people's crates. The only catch is that you have to provide a definition of the type for Schemars's derive to process.
|
||||
|
||||
This is the same way that Serde allows remote deriving, which is why this page reads so similarly to [Serde's documentation](https://serde.rs/remote-derive.html)!
|
||||
|
||||
{% include example.md name="remote_derive" %}
|
Loading…
Add table
Add a link
Reference in a new issue