[cppgraphqlgen] Update to v3.3.0 #14842
Merged
Conversation
This file contains 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
JonLiu1993
added
the
category:port-update
JonLiu1993
requested review from
JackBoosY
and removed request for
JonLiu1993
|
See my comment #14841 (comment) |
wravery
force-pushed
the
cppgraphqlgen
branch
from
19dc8e7 to
740803e
Compare
ras0219
approved these changes
Dec 6, 2020
JackBoosY
suggested changes
Dec 7, 2020
JackBoosY
approved these changes
Dec 7, 2020
|
Thanks for your contribution! |
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.
Describe the pull request
Updates to the v3.3.0 release of https://github.com/microsoft/cppgraphqlgen. This has been tested along with #14841 on Windows, Mac, and Linux, but it works with the prior version of PEGTL as well.
This version has the same
std::filesystemauto-detection forschemagenas PEGTL in #14841. It should work on any target triplet and with all of the runners in the CI workflow.Yes.