feat: authentication with Next Auth #8
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Descrição
Experimentando com Next Auth para autenticação. Relacionado com #6
Pessoalmente, achei o Next Auth interessante mas um pouco intrusivo. Precisa de banco de dados obrigatoriamente e o suporte a TS ainda está sendo feito (nextauthjs/next-auth#220).
A API pública vai um pouco contra alguns styleguides (como por exemplo nomear as funções em
UpperCamelCasesem serem construtores).De qualquer maneira, parece uma solução bem interessante e completa.
Esse PR está longe de estar perfeito, por isso estou abrindo como draft PR.
O que falta ainda é garantir que a autenticação aconteça no server-side também (usando getSession).
Demo