agkountis / listr Goto Github PK

Description

Listr's authentication implementation was done by following an online tutorial. This may not be the optimal way to do proper authentication. We need to understand the industry standards when it comes to authentication and implement a better solution if any.

Goals

• Read up on OAuth2 and JWT.
• Research best practices for authentication in modern web apps.
• Analyse the current implementation.
• Suggest alternative/better solution
• Outline implementation and create new Github issues.

Description

Current components in the front end are not optimaly architected.

Goals

• Read through the existing implementation indentify reusable pieces of functionality and extract it to new components
• Convert function components to normal components if their logic is too complex to be handled by yew hooks.
• Try using message passing to decouple components from eachother possibly using yew agents (pub/sub etc)

Description

The ActionInput component needs to be able to execute validation on the user's input.

Requirements

• The validation logic should not be tightly coupled with the Component itself.
• The component should accept a validation function as a property.

Description

Currently the front end has 0 error handling. It uses expect() and unwrap() everywhere. This is obviously not ideal.

Goals

• Read up on error handling in Rust and identify crates that could be used for error handling in the front end. (Try the anyhow and thiserror crates)
• Read up on how to properly propagate and display errors in yew components.
• Implement error handling for the multiple points of failure in the frontend.

Description

The project needs integration with a CSS framework. Research and implement the best solution to achieve this.

Requirements

Using the bootstrap5 and TailwindCSS experiments done here add CSS integration to the listr-frontend crate.