Major Refactoring

[AkeemAllen]

As the maintainer of wikigen, I need more logging, error handling and testing to improve debugging and mitigate/prevent regressions. General Refactorings

Testing

• [x] Separate Data gathering (input) from processing in rust layer to allow better testing.
• [x] Pokemon Page Generator functions
• [x] Route Page Generator functions

Error Handling and Logging

• [x] Add error handling to all functions that can fail and potentially hang a process.
• [x] Send all error or success messages from the rust layer.
• [x] Keep better track of errors in a file (consider a way of collecting and analysing errors, such as sending back analytics)
• [x] Remove all potentially dangerous unwraps
• [x] Redesign toast store message
• [x] Implement toast message redesign everywhere

Code Quality. Cleanup code where it's need cleanup IMO.

• [ ] Speed
• [ ] Readability
• [ ] Sensible naming conventions and structures
• [ ] Idiomatic Rust
• [ ] Rust Best Practicees

Migrations

• [ ] Rethink and determine more convenient way of handling migrations without needing to continually update code.
• [ ] Keep track of migrations to database and files to know when they have already been applied

Groups to refactor

• [ ] Pokemon Page
• [ ] Pokemon generator functions
• [ ] Route Page
• [ ] Items Page
• [ ] Ability Page
• [ ] Nature Page

[AkeemAllen]

Note: Come up with structure for success execution results that are meant to go back to the JS layer.

Handle Errors as strings?

[AkeemAllen]

Handling update/migrations

• Create button to allow for update from frontend
• When clicked, it will run any migrations and restart the app.

[AkeemAllen]

Organization guide for variable declaration in svelte componente

1. logical groupings
2. let declarations and their derived counterparts
3. const declarations
4. functions