Create a real world tutorial to help everybody understand Laravel Lighthouse step by step

[wolfiton]

I am willing to provide most of the code to create a functional blog with auth using vue-apollo
What problem does this feature proposal attempt to solve?
This solves the getting started and the tutorial section of the docs with a real-world example, That will make more people or companies adopt Laravel Lighthouse into their projects.

The docs and tutorials are not very detailed on how to solve certain important features that you will find in a real-world app.
Which possible solutions should be considered?
Creating a real-world blog to show the value of Laravel Lighthouse

I don't know any other solutions to this problem.

Thanks for looking over my proposal.

[lorado]

Same as for upload example - go ahead and create it in extra repo. You could actually use the repo you already created for upload, and extend it. We could somewhere link your project in docs.

There is one thing makes me warily - as lighthouse grow and probably change some APIs, or introduce some new stuff, that breaks old stuff, you have to update your example. Do you think you can keep your example up to date?

[spawnia]

Have you looked at https://github.com/nuwave/lighthouse-example yet? It is a quite minimal example I created according to best practices I found.

It can be more complete for sure. A comprehensive overview would help greatly, too. I put a great focus on implementing proper tests for it to ensure that the example code actually works.

[wolfiton]

Same as for upload example - go ahead and create it in extra repo. You could actually use the repo you already created for upload, and extend it. We could somewhere link your project in docs.

There is one thing makes me warily - as lighthouse grow and probably change some APIs, or introduce some new stuff, that breaks old stuff, you have to update your example. Do you think you can keep your example up to date?

I will keep it up to date because I want to learn it so I can use it in production in my own apps.
If you guys continue to offer support than we can definitely make something great.

I think in this way we all win:

• the projects get a very detailed documentation fewer questions unanswered, more contributors
• I get to learn Lighthouse and contribute to the docs at the same time.
  That was my exact thouth @lorado, to extend what i actually have already and make it real world. In the end we might be able to use it as a personal blog that is much more secure than WordPress for example.

Thanks for the quick feedback on this.

[genesiscz]

Have you looked at https://github.com/nuwave/lighthouse-example yet? It is a quite minimal example I created according to best practices I found.

It can be more complete for sure. A comprehensive overview would help greatly, too. I put a great focus on implementing proper tests for it to ensure that the example code actually works.

There are a lot of things not used/answered, such as whole app/GraphQL directory possibilities.
First thing that comes to my mind is, add an updatePost so only you, as a logged in user, can update the post.

[spawnia]

@genesiscz open for PR's that add bits of functionality to the example project!

[genesiscz]

@genesiscz open for PR's that add bits of functionality to the example project!

I'd love to contribute, trust me, but my comment was more from the observer & someone who request this from somebody who knows the correct way to do something. I am using types, Queries, Mutation classes, but I am not sure I use them correctly or what are the possibilities. For example, I am not sure how is the BatchLoader used (I know there's a resource for that, but we're talking about the example here)

[wolfiton]

Does someone have any pointers on how to add sanctum to this current example?
It uses vue fro frontend and Lighthouse for backend this also closes the example on how to upload using lighthouse.

https://github.com/wolfiton/vue-upload

[spawnia]

nuwave/lighthouse-example#9

[wolfiton]

nuwave/lighthouse-example#9

Do I have any context where I can store the toekn and the headers in lighthouse?

[wolfiton]

I already saw this part under security and the example you provided but my problem is how to store everything in the context so i can access them using vue.

Also please take a look at helmet from nodejs to see an example why I am asking for headers.

The link to helmet

[spawnia]

You can use plain old middleware to add HTTP headers.

[wolfiton]

You can use plain old middleware to add HTTP headers.

That is very good, thanks @spawnia,

Now for the tricky part once I create a login mutation, I need to verify that the user has the corresponding role and generate a token ability based on that check, also when the app goes offline or enters PWA mode.
I need to revoke any tokens with:

• create
• delete
• update
  I couldn't find in the docs any solutions to this problem, that is real world.
  I can only leave the show and index abilities active.
  My idea is like this:

Create a custom arg resolver for the mutattion somehoiw bring the middleware and generate token based on roles

Bad idea: To store the role with the token.

Thanks for any insight into this.

[spawnia]

I think you might be conflating concepts here. It is my understanding that the roles in a token are supposed to be relatively static and reflect what the user is authorized to do. Generating that once on Login seems sufficient?