Repository navigation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello maintainer,
thanks for your crate!
Here is a proposal for a new optional feature
copy_doc: the purpose is to copy the doc of the initial structure (and its fields) to the patched structure.The need/use-case is to be able to generate documentation automatically from/on the patched structure.
A typical example is when the expected structure for a http
PATCHverb is, well, aderive(Patch)one, and whenschemarsis used to generate a json-schema of the API. It's nice, then, to have the documentation of the original field in the final schema.Tell me if something else is needed!