graphql-mesh
graphql-mesh copied to clipboard
JSON schema numeric enums test
🚀 Snapshot Release (alpha)
The latest changes of this PR are available as alpha on npm (based on the declared changesets):
| Package | Version | Info |
|---|---|---|
@graphql-mesh/fusion-runtime |
0.2.8-alpha-20240321091912-2c2cef5566414f7aaa99fb2d608c77a3562f6a4b |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/plugin-operation-headers |
0.0.8-alpha-20240321091912-2c2cef5566414f7aaa99fb2d608c77a3562f6a4b |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/plugin-prometheus |
0.98.5-alpha-20240321091912-2c2cef5566414f7aaa99fb2d608c77a3562f6a4b |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/serve-cli |
0.3.9-alpha-20240321091912-2c2cef5566414f7aaa99fb2d608c77a3562f6a4b |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/serve-runtime |
0.2.8-alpha-20240321091912-2c2cef5566414f7aaa99fb2d608c77a3562f6a4b |
npm ↗︎ unpkg ↗︎ |
💻 Website Preview
The latest changes are available as preview in: https://a5401b32.graphql-mesh.pages.dev
This is expected because in GraphQL execution result, the enum value should the one in the schema which is _10 as a string in this case