Graphql

I’ve spent the last year on WealthRelay, a valuation API: portfolios, trades, instrument prices, returns, currency conversion, all behind GraphQL. It has the problem every B2B API has at the start. The first customer doesn’t exist yet, and until one does, every design decision is a guess about what the API is for. So I became the first customer. I collect things - sealed Pokémon product mostly, which I track in Collectr - and the collectibles that have genuinely behaved like an asset class these last couple of years are POP MART blind boxes. A set is twelve figures. One of them is the secret, which you can’t see through the box, and which sells on eBay for a multiple of its siblings. People buy whole cases to complete sets, trade their duplicates, and argue about what their shelf is worth. Every tracker I found answered that with a checklist. None of them treated the shelf as what it is: a portfolio, with a cost basis, a market value and a return. ...

Versions: @rjsf/core v6.6.2 is the current stable release. v5 was a major breaking change from v3/v4 - the validator prop became required and the validator was extracted into @rjsf/validator-ajv8. The code in this article targets v5+. @graphql-codegen/cli v5 is current and the config format shown is compatible. Internal tooling is where good architecture goes to die. Every backfill, every data-correction operation, every admin action ends up with the same choice: write a one-off form, use the GraphQL playground, or write a script. The first option takes hours and is immediately outdated. The second only works if you let engineers near production data. The third requires a developer every time. ...

This approach is based on Nigel Sampson’s post on GraphQL validation metadata, extended with a recursive validation middleware and a codegen pipeline for the frontend. Versions: HotChocolate v16.2.0 is the current stable release. The TypeInterceptor and DirectiveType APIs shown here have been stable since v12 and are unchanged through v16. v15+ dropped .NET 6/7 support - .NET 8 or later is required. The middleware syntax uses C# 12 primary constructors; see the note in that section if you are on an older SDK. ...