-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add DB Docker Setup, Review Readme, Review Auth Function #78
base: master
Are you sure you want to change the base?
Conversation
Thanks, looks good.
But not everybody uses docker and is easier to just install Mongo. Also changing npm to yarn adds another dependency, because you'll need to have yarn first installed to run the project. I think those things should be optional, but I'll let the community decide whats best. |
isAuthenticated: true, | ||
user, | ||
} | ||
} |
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.
Should there be an else to catch if the user does not/ no longer exists. We are getting a jwt that is signed but with an id
that is no longer in the system. The other block where isAuthenticated: false
will not be called since that is in the else
statement for the check for headers.
Also the catch
block for detecting an invalid token should be handled as well? Maybe return a direct error to the user?
Added a comment at a line that confused me. Not sure if I didn't understand the flow or it is a valid concern. The Also in the Roadmap, can you add a tick to "Add agenda dashboard" bullet point as that is available. |
Because you can pass in a .env file to docker (and it gets put in env. variables), it would be possible to check if the env variables are set. If they arent already set, load from .env file. If they are, dont do anything. |
@ent3r I believe it's optional the way it is and the docker solution just simplifies things for some people. You either:
|
Just a suggestion. The goal of this PR is to make it easier for new contributors to write the first few tests which I think is the most important next step.
interesting architecture, congrats