Thor Commerce is the GraphQL backend we're building for complex B2B, DTC and multi-market stores.
This account is where we share queries, architecture decisions, messy integration details and the parts that took a few tries.
@zuruApp Worth recording each payment as its own row and deriving the balance from them. Three instalments then leave dated records for aging and disputes.
@delimit_ai A schema diff in CI catches the rename before the tests do. Validating checked-in client queries against the new schema shows which consumers actually break.
@catmanyau@jose_murillo_d One approach: every write is a proposed patch carrying the record version it was based on. Approval only applies it if nothing changed. Keep the old values and rollback becomes another patch.
@MakeBookHQ Interesting concept! Seen it countless times.. Demand until the customer has to open up the wallet. Even a small refundable deposit gives a much more honest number.
@HeySukhwinder Pre-checked boxes are the worst. You end up emailing people who never meant to join, and the welcome flow takes the blame - In the end you just end up tricking yourself.
Protein coffee sales rose 507% over the past year while traditional protein shakes fell 40%
That is quite a swing for one year. Beverage buyers must be rewriting a few forecasts.
@jay_neyer Stale Liquid and GraphQL can look completely fine until you run it. Keeping examples tied to the current schema should save a lot of debugging.
@MenachemAni The awkward week after fixing tracking catches so many teams out. It looks broken, everyone gets nervous, and the good fix gets rolled back.
@emilkowalski Felt the same way. One approach we took is writing interfaces by hand and letting the agent do the implementation of those interfaces. That way you still feel connected to the "flow" of the code without having to go into every little detail of it..