Conversation
ueco-jb
force-pushed
the
new-schema-0-15
branch
from
fc9bd77 to
fe993e7
Compare
Contributor
I merged the first PR (0.15 upgrade). Unless there are objections, I would tag v0.15.0 now and we can do v0.15.1 with the better schema. |
ueco-jb
force-pushed
the
new-schema-0-15
branch
2 times, most recently
from
a921eae to
a31d246
Compare
Co-authored-by: Simon Warta <2603011+webmaster128@users.noreply.github.com>
ueco-jb
force-pushed
the
new-schema-0-15
branch
from
a31d246 to
5af985a
Compare
ueco-jb
force-pushed
the
new-schema-0-15
branch
from
5af985a to
ec38800
Compare
ueco-jb
changed the title
schema-derive
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
3 participants
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.
follow up of #80
This one is currently kind of blocked because of bug in new schema macro generator which takes generic arguments incorrectly.