When adding a new (not null) column to the users table, it breaks registration with no error

[alarner]

The default registration page and post /auth/register route should return better errors, notifying the developer that a required field was not specified.

For example, create a migration that adds a required (not null) username column to the users table. Run that migration and try to register. Registration fails with no error.

What should happen:

Registration should fail, but it should show a database error or text error giving the developer some information on why the error occurred.

[alarner]

Also there is an issue with the registration. It should be updated to be more flexible so that it doesn't require updating /auth/register route

[alarner]

Fixed by #20 and #22