matthewswain / honestyshop Goto Github PK

This should be considered to keep the code clean, e.g. preventing a duplicate item from being created. This is currently handled in the controller.

When a user attempts to create a duplicate item, they should be warned/redirected. At the moment this causes an exception due to the database's unique constraint.

The init_db function currently adds data for testing. This should be refactored so the function can be used for upgrades in live.

The Active checkbox currently has no code behind it and so Items cannot be made inactive, etc. This needs to be implemented.

It should be possible to configure the app to prevent users registering if their email address is not from the right domain.

It is not obvious to first time users that they register by clicking the link on the login page. The registration process needs to be clearer.

Background

Currently there is no way for users to suggest new snacks they'd like to see in the snack cupboard.

Change

Users should be able to suggest new snacks for the snack cupboard, so that we can get everyone the snacks they want.

Acceptance criteria:

• Normal users should be able to suggest new snacks for the snack cupboard.
• Admin users should be able to see a list of all suggested snacks, and how many uses have suggested each one.

Notes for testing:

• Make sure that users can't see each others' suggestions.

It should be possible to add a favicon.ico to the static directory and have it served appropriately. This should not cause an error if the file doesn't exist.

A user should be able to see payments on the history page, below purchases.

On the item creation page and possibly others, double clicking the save button causes double form submission and so exceptions.

It should be possible to make users inactive, hiding them from the admin summary, preventing them from logging in, etc.

Admins should be able to apply payments to users' accounts.

Admins should be able to view each users history page. They should also have access to a summary page listing users and balances.

The list of users needs to be sorted alphabetically to make it easier to apply payments.

If the secret_key is not set with a quoted string in app.py, gunicorn returns a 500 server error when trying to use sessions.

A user should be able to see their running total, possibly on the history page.

Users are redirected to history when making a purchase. It would be good if there was a quick link to return to the buy page.

A user should be able to reset his/her password via a reset email.

Currently if a user makes a purchase, there is no way for this to be undone. It should be possible for a user to delete purchases to resolve mistakes. This should perhaps be limited to purchases in the last 24 hours.

Currently if a user registers, but the confirmation email process fails, the user cannot login or re-register. Exception handling should be added so that if the registration fails the user and activation token are deleted, allowing the user to re-register.