verencelola / quexl Goto Github PK

Description of Issue

• verify activation token jwt schema

Description of current implementation

• currently, all the user queries are done with a case-sensitive search. The username queries should all be done in lowercase and the usernames should all the saved in lowercase.

Desired refactor.

• implement user queries and saving to use only lowercase comparison.

Current Implementation.

• The current implementation of the application is not optimised to deliver emails faster. It takes a couple of minutes for the email to be delivered and this blocks the content delivery of the API response.

Desired functionality.

• Refactor code to optimise performance. for instance, optimise the user registration view to return response to the client faster.

Description of Issue

• currently, all the hosts are allowed to connect to the Django application. This is a security concern and should be fixed for apps in production.

Proposed Fix/ Implementation

• implement only specific hosts allowed to connect to the backend application

Currently, tests are failing upstream due to database setup. Fix this by adding necessary configuration.

Current implementation

• currently, the user can update/ set order status as
  • started,
  • canceled
  • delivered
  • accepted
  • completed
  • archived

Desired implementation

• During order creation, the default status for a given order should be set to started.
• The order creator should be able to only update the status order their order to canceled or delivered
• Only the superuser should be able to update all the status of a given order.
• Once the order is marked as delivered by the seller, the buyer can set the order status to accepted or completed. If the order is marked as declined, the order on the seller side is marked as automatically archived.

IssueI Overview

Currently, as implemented #10, the number of user roles and permissions available in the project are fixed and can never be changed without changing the codebase. This implementation is impractical in that the project requirements - user roles and permissions might change later after the application is already in production.

Expected Implementation

To address the issue described above, the application should have a means of editing/ adding and deleting user roles and permissions besides just allowing roles and permissions management for individual users.

Current Implementation.

Currently the user can make only one payment per order placed.

Desired implementation.

The users should be able to make more than one payments per given order.