Schema null config about lighthouse-graphql-passport-auth

[dali546]

Workaround:

I did bypass this by modifying lighthouse-graphql-passport.php config:
'schema' => config('lighthouse.schema.register'),

This will then use the lighthouse default schema.

There was one issue though. If the default schema in lighthouse.php is auth.graphql I get the following error

   GraphQL\Error\InvariantViolation  : The root Query type must be present in the schema.

  at /mnt/data/DATA/Community/Community-Server/vendor/nuwave/lighthouse/src/Schema/SchemaBuilder.php:82
    78|             }
    79|         }
    80| 
    81|         if (empty($queryType)) {
  > 82|             throw new InvariantViolation(
    83|                 'The root Query type must be present in the schema.'
    84|             );
    85|         }
    86| 

  Exception trace:

  1   Nuwave\Lighthouse\Schema\SchemaBuilder::build(Object(Nuwave\Lighthouse\Schema\AST\DocumentAST))
      /mnt/data/DATA/Community/Community-Server/vendor/nuwave/lighthouse/src/GraphQL.php:242

The workaround to that was to use my normal schema.graphql and import auth.graphql to it.

[joselfonseca]

Hello the and thanks for the question.

So you can define your own schema by setting the file path in your config, when you publish the package config also the default schema is published so you can set the type to what ever you need. This is demonstrated in this article

https://ditecnologia.com/2019/06/24/graphql-auth-with-passport-and-lighthouse-php/

The reason for the schema to be registered and use all those defaults is for convenience, but it is also fully customizable as you can see in the article.

Let me know if that answer your question to close this issue or if you need more guidance in your specific use case.

Thanks!

[dali546]

Yes it is ok to close. The issue I was facing is that I went ahead and created my own schema, but failed to update the config.

My assumption was that if i published the schema and config, the config should automatically use my schema. I see now after re reading the readme it does say the config should be updated. good to close

[mustafa-kahraman]

If you don't have Mutation type at your master schema file... you can NOT extend your schema with Auth schema cuz it has extend type Mutation type which there is nothing to extend...