This repo includes reproduction examples of a few mesh bugs
nvm use
for d in ./*/ ; do (cd "$d" && yarn); done
This is a working example to start from
cd working-mesh-helix && yarn && yarn test
Tests pass 🎉
When 2 status codes have the same response type, e.g. 200 & 400, the 400 wont be handled nicely
cd same-response-issue && yarn && yarn test
Get "HTTP Error: 400, Could not invoke operation GET /pet/{args.petId}"
instead of it returning the data as unioned response
When You have 2 sources, but only 1 has naming convention transform, it errors when building mesh
cd missing-naming-convention && yarn && yarn test
Get error Error: Unable to merge GraphQL directive "httpOperation"
When using bare namingConvention transform, enums arnt converted to their original casing before being sent to upstream
cd bare-enum-sending && yarn && yarn test
Upstream server gets enum value FLUFFYBOI
instead of FluffyBoi
which it wants
When using bare namingConvention transform, get error "Cannot read properties of undefined (reading 'originalName')"
cd naming-convention-originalName && yarn && yarn test
Get error "Cannot read properties of undefined (reading 'originalName')"
Renaming a type within an union causes error
cd union-renaming && yarn && yarn test
Get error Abstract type \"pet_by_petId_response\" was resolved to a type \"ServerError\" that does not exist inside the schema.
Dates are converted to UTC
Issue: ardatan/graphql-mesh#5229
cd datetime-timezone && yarn && yarn test
Get 2016-02-01T11:00:00.000Z
instead of 2016-02-01T00:00:00-11:00
Build mesh gets typescript error
cd ts-artifacts && yarn && yarn test
Get error TypeError: Cannot read properties of undefined (reading 'get')