xogroup / joi2gql Goto Github PK

1. Take a more defensive approach to traversing deeply nested properties. Should use Hoek.reach() api.

2. Refactor unit and integration tests. Remove GITS references.

Context

• node version: 8
• environment (node, browser): node

What are you trying to achieve or the steps to reproduce ?

const Joi2GQL = require('joi2gql');
const Joi = require('joi');
const schema = Joi.object().keys({
    prop1: Joi.string().lowercase(),
    prop2: Joi.number().integer(),
    prop3: Joi.object().keys({
        key1: Joi.string(),
        key2: Joi.string()
    })
});

const Schema = Joi2GQL.transmuteType(schema);
const gqlschema = {
    query: {
        schema: Schema
    }
}
const mySchema = Joi2GQL.transmuteSchema(gqlschema);

What result did you expect ?

For a valid GraphQL object to be returned

What result did you observe ?

// Anon.prop1 field type must be Output Type but got: undefined

Over on Gatsby I've been upgrading joi to the latest version. However this is the final holdout to make that happen. It looks like there are a number of changes made to joi that make this library incompatible.

Things like schema._tests and schema._flags aren't supported as they are for internal use.

Are there any plans to support the latest joi?

https://github.com/hapijs/joi/blob/v10.6.0/API.md#lazyfn---inherits-from-any

Example Schema

const schema = Joi.object().keys({
  name: Joi.string,
  age : Joi.number().integer()
  team: Joi.array().items(Joi.lazy(() => schema)
})

Support all scalar/definition types in type-dictionary

Scalar

• GraphQLInt,
• GraphQLFloat,
• GraphQLString,
• GraphQLBoolean,
• GraphQLID

Definitions

• GraphQLScalarType,
• GraphQLObjectType,
• GraphQLInterfaceType,
• GraphQLUnionType,
• GraphQLEnumType,
• GraphQLInputObjectType,
• GraphQLList,
• GraphQLNonNull,
• GraphQLDirective,

Context

• node version: 18.5
• environment (node, browser): chrome
• any relevant modules used with express, express-graphql
• any other relevant information:

I was thinking of using this package in a live project but it was last updated 5 years ago so I was wondering when you are going to update it?

Context

• node version:
• environment (node, browser):
• any relevant modules used with (hapi, hoek, etc.):
• any other relevant information:

What are you trying to achieve or the steps to reproduce ?

What result did you expect ?

What result did you observe ?

Vodou. That could be cool

Context

• node version:
• environment (node, browser):
• any relevant modules used with (hapi, hoek, etc.):
• any other relevant information:

What are you trying to achieve or the steps to reproduce ?

What result did you expect ?

What result did you observe ?

Context

• node version:
• environment (node, browser):
• any relevant modules used with (hapi, hoek, etc.):
• any other relevant information:

What are you trying to achieve or the steps to reproduce ?

What result did you expect ?

What result did you observe ?

Context

• node version:
• environment (node, browser):
• any relevant modules used with (hapi, hoek, etc.):
• any other relevant information:

What are you trying to achieve or the steps to reproduce ?

What result did you expect ?

What result did you observe ?

Context

• node version:
• environment (node, browser):
• any relevant modules used with (hapi, hoek, etc.):
• any other relevant information:

What are you trying to achieve or the steps to reproduce ?

What result did you expect ?

What result did you observe ?

Gitbook Might be overkill, but looks nice.