Plans for cppgraphqlgen 5.0

まだ誰も着手していません。

next ブランチから始め、残っている未チェック項目 #330 を、関連付けられた議論および完了済みの 5.0 チェックリスト項目と合わせて確認してください。この issue は、自己完結したタスクではなく、API の破壊的変更、C++20/C++23 の採用、代替の JSONResponse 実装を追跡するための広範な計画です。完了 여부は選択した具体的な機能に依存します。

索引モデルが issue の本文から書いたものです。

This is where I'm going to start tracking features for 5.0, the next major version of cppgraphqlgen. This will be a breaking change for existing consumers, so it's an opportunity to cleanup deprecated methods and simplify some of the APIs. I'm also going to adopt a few more C++20 and C++23 features if they are well enough supported on Windows, Linux, and macOS now.

This is using #172, the tracking issue for cppgraphqlgen 4.0, as a template and starting point.

Stand up a branch for 5.0 and start making PRs against that: https://github.com/microsoft/cppgraphqlgen/tree/next.
C++20: Modules.
C++20: Ranges: Should modernize a lot of begin/end iterator usage.
C++20: std::fmt instead of std::ostringstream.
C++20: Co-routines/Awaitable interoperability: See #271, this may require a breaking change to the cppgraphqlgen Awaitable types.
Sharing input/scalar/enum types between clientgen and schemagen: See #264 for more discussion.
Build some alternate implementations of JSONResponse.* with other JSON libraries besides RapidJSON.
#320
#321
#323
#330

I'll update this list as new features crop up and as I/we make progress on it. If there's something you'd like to see that I haven't included already, feel free to comment on this issue.

評価

調査の方向性

説明

コントリビューションガイド

はじめの一歩

microsoft/cppgraphqlgen のほかの issue

似ている issue