Markus Podar

@hailwood thanks for your insights I noticed lighthouse in the meantime and it seems radically different on some parts. However one reason why it's great to get started with Folklore...

You might be interested that lighthouse is currently working on an implementation, still a PR though : https://github.com/nuwave/lighthouse/pull/337

Duplicate of https://github.com/Folkloreatelier/laravel-graphql/issues/382

And your coverage setup is working, in general? For non-GraphQL related stuff? A project of mine I work on has working coverage also within the GraphQL parts.

> Laravel 5.7.7 (clean install) > laravel-graphql 1.1.0 How did you do this? The latest 1.1.0 release isn't compatible (composer version constraint) with 5.7, i.e. it won't install? This is...

> In the meantime I should add that, failure in authentication should normally result in the status code of 401 (unauthenticated) but laravelgraphql wouldn't do that and return 200 (ok)...

For one, nothing in your resolver prevents you from simply calling `request()` and access it; though personally I don't recommend this approach. ---- A better approach is to make use...

Although I'm not using lighthouse, unfortunately I have an opinion 😄 > How do you think, is it hard to transfer a project from folklore package to nuawe package? I...

> every time we need to drop vendor/folklore in order to run `composer update` You can work this around. Composer allows to specify "repositories" and by basically copying the composer.json...

You can replace the controller/method being called and basically can return anything you want, see https://github.com/Folkloreatelier/laravel-graphql/blob/0fee73c9855bc4f59a4977ffbd34a83f4ee99593/src/config/config.php#L37-L49