-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial docs on auth #1616
base: main
Are you sure you want to change the base?
Initial docs on auth #1616
Conversation
May you consider adding an item to demonstrate how protected routes works? |
Alright, i updated the docs to remove the redundant section, and instead link out to the example. In addition, i added documentation on linking to a deno fresh kv oauth plugin to use: https://deno.land/x/deno_fresh_kv_oauth |
To quickly configure your application using a Deno Fresh plugin, you can see the | ||
documentation for the | ||
[Deno Fresh KV Auth plugin](https://deno.land/x/deno_fresh_kv_oauth). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deno KV OAuth will soon be getting an official Fresh plugin. Can you please hold off on this part? 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Fresh plugin has been added to Deno KV OAuth. Check out the docs here: https://github.com/denoland/deno_kv_oauth#getting-started-with-fresh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: this link now guides users in creating their own plugin. Also, note that the deno_fresh_kv_oauth
plugin is a third-party plugin, as the official Deno KV OAuth Fresh plugin has been removed.
This is by no means complete, but thought a PR to show the code direction of the Auth docs would be good. I started by targeting the two links provided in issue #1612 and also included some information from this blog.