nuwave / lighthouse-docs Goto Github PK

This would be helpful for users that are coming from a REST background or are migrating an existing REST api.

Related Issue/PR from the main repo

no

Lighthouse Version

next / master

The directive where has a duplicated description from the whereBetween.

this way you dont have to go back & forth between all the items to find what u r after, especially that the pages are not loaded vie pjax or a js router which means all the assets need to be reloaded on each section u visit.

GraphQL is still very new for many users. Rather then add our own explanation/tutorial, we might just link to some pre-selected resources.

@chrissm79, Can you help?

Never used Gatsby but wanted to try out, do I need extra configuration like some Apollo, database, etc..?

Its possibly I only have to touch the V2 pages markdowns?

Since validation is a substantial part of any API, we should add the @rules directive to the docs. Possibly a complete section dedicated to validation?

Related Issue/PR from the main repo

Link to related Issue/PR this PR corresponds to

Lighthouse Version

Which version of Lighthouse does this apply to?

https://lighthouse-php.com/ -> https://lighthouse-php.com/4.11/getting-started/installation.html

It's showing 404 if I go to the page by right click and hit open in new tab from the main page.

Browser: Google Chrome Version 80.0.3987.149 (Official Build) (64-bit)

Please compare the docs on master and v2.1 for the directive @belongsTo. The master version is missing the part with the GraphQL example.

This is a good way for non package developers keep tracking of improvements between versions.

Making a diff on master branch from main package can be painful.

Adding a section for packages in our documentation.
Maybe do this automatically based on a tag on github?

What you think @hailwood ? upvotes?

Copying the issue from @yaquawa

I've been looking around the source code of lighthouse for a while, and I found that if a field resolver is not provided from directive, lighthouse will fallback to the 'config.lighthouse.namespaces' implicitly according to the type of the root type and object type, which I found it's really really useful, because then I don't need to write directive everywhere… I really like this kind of "ruby on rails" style.

But this feature is not described in the doc yet. Why not…?😿

Related Issue/PR from the main repo

nuwave/lighthouse#288
Lighthouse Version

All

The lighthouse site shows on top v2.1.

https://lighthouse-php.netlify.com

Please change the contrast of the colors. color: #880000 is really hard to read (for me at least) on a background-color: #2b2644.

or atleast make the background-color of select to something that gives better contrast.

Thanks in advance! 👍

Hey @chrissm79 ,

New docs are A+

Was thinking maybe we could add an example query using each directive to give the users a clearer understanding of how applying it manipulates the query.

Thoughts?

See nuwave/lighthouse#219

It would be great if from the start a new user has an idea what is available (e.g. https://github.com/mll-lab/laravel-graphql-playground as mentioned in nuwave/lighthouse#219 (comment) ).