C++ GraphQL schema service generator
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.5...v4.5.6
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.4...v4.5.5
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.3...v4.5.4
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.2...v4.5.3
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.1...v4.5.2
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.0...v4.5.1
The most notable change was part of the fix for #254 in #256. In the course of debugging it, I realized that response::IdType was being overly aggressive about trying to interpret any string that was a valid Base64 encoding as a Base64 encoded vector of bytes:
I'm bumping the minor version because
response::IdTypein inputs/arguments is going to be a string all the time internally, and that changes which accessors you can use on field arguments. It's generally more consistent now, but if you are used to using it with Base64 encoded binaries and your code assumes that's what it contains, you may need to perform the conversion explicitly withargId.release<response::IdType::ByteData>()rather than using theconstByteDataaccessors. You can still useresponse::IdType::isBase64()to tell if it's safe to release it as a binary (otherwise it will throw an exception for strings which are not valid Base64 encodings), and it's always safe to release it as a string. It's also always safe to use theconstc_str()OpaqueStringaccessor onresponse::IdTypefield arguments now because they are guaranteed to hold a string internally.
The
response::IdType::ByteDatatype is just an alias forstd::vector<std::uint8_t>, which was the original type forresponse::IdTypebefore I addedstd::stringsupport, so you could also write thereleasecall asargId.release<std::vector<std::uint8_t>>()if that looks better to you. The same applies toresponse::IdType::OpaqueStringvs.std::string.
Otherwise, most of the changes since v4.4.1 have to do with fixing warnings and errors that showed up when enabling LTO (link-time-optimization) in GCC 10 and 12. The project, including all samples and tests, should now build cleanly with GCC using the -flto=auto compiler flag.
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.4.1...v4.5.0
Till the try/catch/rethrow handling is fixed in the PEGTL version of parse_tree, throwing an exception during parsing easily overflows the stack on Windows with MSVC. This change brings a simplified version of the PEGTL parse_tree into cppgraphqlgen without support for the unwind feature (which cppgraphqlgen doesn't use), so it no longer needs to handle the exceptions at each level of the tree. It just lets them be caught directly in the caller after destroying all of the objects on the stack.
The short version is that this should fix #222 using the default depth limit of 25 (or even up to ~100) rather than needing to set it to something less than 10. If/when PEGTL is updated to remove the try/catch/rethrow implementation, cppgraphqlgen can revert to using the original version of parse_tree in PEGTL.
This version also updates the PEGTL sub-module and find_package call in CMake to use 3.2.6, which has some fixes for recent versions of both MSVC and GCC. If you have a CI build which uses cppgraphqlgen and PEGTL (e.g. from vcpkg), you may have noticed that it broke recently when Visual Studio was updated. This should fix that, too.
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.4.0...v4.4.1
This is a minor version update because the code does need to be regenerated with schemagen/clientgen to maintain compatibility with the GraphQLService.h/GraphQLClient.h shared headers.
There's also a fix for a command line parsing bug in clientgen (#248) and several small documentation fixes to match changes in behavior or improve clarity.
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.3.1...v4.4.0
response::IdType accessors for backwards compatibility by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/245
Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.3.0...v4.3.1