Organized the code and enhanced error handling #10
No reviewers
Labels
No labels
bug
duplicate
enhancement
fix
good first issue
help wanted
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
xinux/relago!10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/general-report_lib"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The code is more organized now and better error handling
Motivation
The code had many noisy aspects and clumsily written. So that, we needed to fix that
What have I done
We have been using
create_reportfunction to create report. Due to our views, it's unnecessary fp idiom which has become complex code to read and maintain. So, I builtReportBuilderwhich switches our previouscreate_reportfunction to more organized and close to Rust idiom code.Besides, I prevented many potentially error panics and converted to organized error handling :)
@ -302,3 +302,2 @@.register(async move {let conn = Connection::system().await.unwrap();let proxy = crate::DaemonServiceProxy::new(&conn).await.unwrap();let conn = match Connection::system().await {Here fixed already
bcb6b1de5b/crates/gui/src/window/mod.rsYou can show in my PR: #6/files
I will merge these PRs and keep the best solutions while fixing conflicts
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.