rafase282/mangadb

A Secured RESTful API Service for Manga

Rafase282

This is my official portfolio. It was created using my Generator.

mangadb's Issues

Add email capabilities

Add email support for handling password reset and for sending news to users.

Generate API stubs with swagger

Provide functionality to the swagger ui to test the api from there directly.

Bonus: Upgrade to swagger 2

Forgotten Password Mechanism

Being able to handle a forgotten password request would be highly beneficial. See here for a guide.

Use passwordless

Using passwordless could be a good idea, particularly if email functionality is provided.

Create API Documentation

A better documentation is required for the API. The wiki can be used, but a summary or get started is needed for the readmen.md.

The vision that I have is a quick get started for the readme and then have it with links to its own wiki with detailed documentation and examples.

Allow for more than one admin to be declared

Feature Request

Having more than one admin account might be something other might want.

User deletion also deletes its mangas

Make the deleting of the user also delete the user's manga instead of using a dedicated route for deleting its mangas.

Note that having two separate routes allows for the admin to delete all the mangas without deleting the user.

Enhance temp JWT

Allow to provide a URL so that a link can be provided aside from the token itself for usage with front end clients thus enabling them to provide a password reset without the user having to do anything outside of the browser or requiring expertise.

Add password recovery functionality

Because there is always the case when a user needs to change it.

If using passwordless, then change email instead of password?

Does it work?

Does this still work?

Implement Test

having test to the API functionality will be great and seems to be a standard for good software.

Use TDD to test all api calls

The test file should test for all routes and functionality.

Switch schema and routes

Manga Schemas should not have unique fields, this allows multiple users to have the same manga.

Routes for mangas should then use id instead of title.

Create new route to retrieve list of mangas with the same title for a user.

Add swagger UI

Add swagger UI Support

[Feature Request] Validate E-Mails without having to send emails

Use an external service or create your own that will validate and verify emails without having to actually compose and email and send it to verify after the user clicks on a generated link to confirm email.

Basically no user interaction needed to validate and verify the email. See here for an example of such service like http://quickemailverification.com/

Email Verification Mechanism

A nice feature would be to verify emails so the user gets to check his email and click a link to verify his account. This will keep the created user as a temporary user that gets set as a regular user after the email is verified. Otherwise, the user will not have access to the services.

Check email-verification for a npm package that does just this. I have been having trouble with it, mostly the email part.

Code example here.