cppgraphqlgen

What's Changed

• fix: #306 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/307
• fix: #304 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/308
• fix: input type member default init error on clang 14 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/310

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.7...v4.5.8

What's Changed

• Couple of bug fixes by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/303

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.6...v4.5.7

What's Changed

• Fallback to parsing out-of-bounds 32-bit integers in JSON as doubles by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/296

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.5...v4.5.6

What's Changed

• Make workflows work with vcpkg binary artifact caching by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/293
• Make the vcpkg rapidjson dependency conditional on a feature by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/294

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.4...v4.5.5

What's Changed

• Fix DLL export attribute order for clang on Windows by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/292

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.3...v4.5.4

What's Changed

• Call find_package(PEGTL) implicitly from find_package(cppgraphqlgen CONFIG) by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/289

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.2...v4.5.3

What's Changed

• Default arguments break for incomplete struct definitions in input types by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/282
• Add an HTTP client/server sample with Boost.Beast by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/283
• Improve awaitable errors by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/285
• Fixing SonarQube static analysis warnings by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/286
• Export compile commands and fix some SonarLint warnings by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/287

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.5.1...v4.5.2

What's Changed

• Fix #265 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/266
• Expose a Traits struct for each client operation for easier templating by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/273
• Fixing bugs and CI workflows by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/279

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::IdType in 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 with argId.release<response::IdType::ByteData>() rather than using the const ByteData accessors. You can still use response::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 the const c_str() OpaqueString accessor on response::IdType field arguments now because they are guaranteed to hold a string internally.

The response::IdType::ByteData type is just an alias for std::vector<std::uint8_t>, which was the original type for response::IdType before I added std::string support, so you could also write the release call as argId.release<std::vector<std::uint8_t>>() if that looks better to you. The same applies to response::IdType::OpaqueString vs. 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.

What's Changed

• Update PEGTL version number in README by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/253
• Fix source lifetime and preserve input strings in response::IdType by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/256
• Miscellaneous warnings and errors which showed up in GCC 12 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/257
• Adding Microsoft SECURITY.MD by @microsoft-github-policy-service in https://github.com/microsoft/cppgraphqlgen/pull/259
• Cleanup redundant inline specifiers by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/262

New Contributors

• @microsoft-github-policy-service made their first contribution in https://github.com/microsoft/cppgraphqlgen/pull/259

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.

What's Changed

• Customize the PEGTL parse_tree implementation by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/252

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.

What's Changed

• Fix #248 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/250
• Use concepts and type traits instead of specializing service::isInputType() for each input type by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/249
• Clarify clientgen usage in latest version by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/251

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.3.1...v4.4.0

What's Changed

• Add response::IdType accessors for backwards compatibility by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/245
• Generate input type copy constructors by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/247

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.3.0...v4.3.1

Possible Breaking Changes

Most users should not notice the difference, but there are a few things that might require changes to your code or build settings:

• Almost every struct and method/function that returns anything is now decorated with [[nodiscard]], so you may get compiler warnings where you did not before. If you treat warnings as errors, this could also break your build.
• The [[nodiscard]] annotations led me to notice that I was not checking the result of the ResolverContext::NotifySubscribe/ResolverContext::NotifyUnsubscribe resolvers in subscribe/unsubscribe. I decided in https://github.com/microsoft/cppgraphqlgen/commit/63ef2ce08c5804aa42dbfefcb22cfd137d696cd6 that subscribe/unsubscribe ought to propagate the errors by throwing an exception. If you have a default subscription object and it does not handle every field gracefully in the ResolverContext::NotifySubscribe/ResolverContext::NotifyUnsubscribe case (for instance you are using the NYI generated stubs which throw exceptions), you may need to work around that. The changes in https://github.com/microsoft/cppgraphqlgen/pull/240 allow a couple of ways to do that:
  • If you do not handle the ResolverContext::NotifySubscribe/ResolverContext::NotifyUnsubscribe resolver calls, you can leave the default subscription object on Operations empty and it will skip that call. You need to override the default (empty) subscription object in each call to deliver if you were not already doing that, since the default subscription object is also used by deliver in the absence of an override.
  • You can override the subscription object used for ResolverContext::NotifySubscribe/ResolverContext::NotifyUnsubscribe now in subscribe/unsubscribe, as an additional member in RequestSubscribeParams/RequestUnsubscribeParams.
• PR https://github.com/microsoft/cppgraphqlgen/pull/241 added support for generating multiple operation objects in a single request document from clientgen. Part of that involved moving the enum and input type declarations to a shared namespace (already specified with the --namespace parameter). They are re-exposed with using statements in the per-operation namespace, but since the input types used to be declared inline as part of the Variables struct, you may need to remove the Variables:: scope from code which references them. You can now reference them from either the --namespace shared namespace or the per-operation namespace which still contains the Variables struct.

What's Changed

• Add a migration guide from v3.x to v4.x by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/236
• Add constexpr support to internal::sorted_map and internal::sorted_set by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/237
• Make the default subscription object optional and allow an override for subscribe/unsubscribe by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/240
• Output all operations from clientgen if the --operation flag is not specified by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/241
• Code cleanup by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/242
• Update docs for next release by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/243

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.2.0...v4.3.0

I had to make a few changes that may be incompatible with existing consumers, but they are small enough that I think this can be considered a minor version update rather than a full major version. The changes which are most likely to affect existing code are the updates to response::IdType (see changes to how the fake ID's are initialized in TodayMock.cpp), and how nullable nested input types are represented as std::unique_ptr instead of std::optional to support cycles of nullable/list input types (see changes in ClientTests.cpp where it initializes the Variables::CompleteTaskInput variable).

What's Changed

• Fixes for #208 and #209 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/214
• Make CMake old-file cleanup safer/more specific by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/215
• Update PEGTL submodule to 3.2.5 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/219
• Add a unit test for invalid string escape sequences by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/223
• Adds a virtual default destructor for RequestState by @ALTinners in https://github.com/microsoft/cppgraphqlgen/pull/228
• Add a configurable depth limit to the parser by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/231
• Accept either a Base64 encoded binary or an opaque string in response::IdType by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/232
• Options to remove base64 ID encoding at compile time by @ALTinners in https://github.com/microsoft/cppgraphqlgen/pull/229
• More constexpr schema by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/234
• More constexpr schema by @ALTinners in https://github.com/microsoft/cppgraphqlgen/pull/227
• Input type references by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/235

New Contributors

• @ALTinners made their first contribution in https://github.com/microsoft/cppgraphqlgen/pull/228

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.1.1...v4.2.0

What's Changed

• Don't add Variables:: scope to scalar and built-in types in clientgen by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/202
• Make Request/Operations methods thread-safe and test custom awaitables by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/204
• Bump patch version for bugfix release by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/207

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.1.0...v4.1.1

What's Changed

• Don't add Variables:: scope to scalar and built-in types in clientgen by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/203
• Make Request/Operations methods thread-safe by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/205
• Bump patch version for bugfix release by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/206

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v3.7.0...v3.7.1

What's Changed

• Enable strict compiler warnings and fix resulting warnings/errors by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/194
• Reset the mock service state for each test by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/195
• Merge graphintrospection lib back into graphqlservice by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/197
• Consolidate TodayMock services and protect async loaders with mutex by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/198

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.0.1...v4.1.0

What's Changed

• schemagen bug fixes and cleanup by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/193

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v4.0.0...v4.0.1

What's Changed

• Add default fallthrough cases by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/166
• Add a learn_star_wars sample based on https://graphql.org/learn/ by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/168
• Merge work in progress from personal fork to start working on 4.0 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/173
• More progress on 4.0 tasks by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/174
• More progress on 4.0 tasks by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/175
• Include fewer/smaller headers to speed up build by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/176
• Remove the schemagen --merge-files option and make everything use separate files by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/177
• Update to October 2021 release of the GraphQL spec by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/179
• Implement delivery by SubscriptionKey and a type-erased JSON writer interface by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/180
• Allow field getters to return a std::shared_ptr by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/181
• Distinguish AwaitableScalar from AwaitableObject by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/183
• Only install new CMake files for install configs by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/184
• Minor fixes from testing with the vcpkg port and gqlmapi by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/185
• Documentation pass and a little bit of code cleanup by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/186
• Fix some code analysis issues detected by VS 2022 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/187
• Bring v4.0.0 to the main branch by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/188
• Re-use the same Library.rc.in and Generator.rc.in files across targets by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/189

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v3.6.0...v4.0.0

What's Changed

• Add default fallthrough cases by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/166
• Add a learn_star_wars sample based on https://graphql.org/learn/ by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/168
• Backport compatible changes from v4.0.0 to v3.7.0 by @wravery in https://github.com/microsoft/cppgraphqlgen/pull/190

Full Changelog: https://github.com/microsoft/cppgraphqlgen/compare/v3.6.0...v3.7.0