Add export list context menu item #59
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
edfloreshz/tasks!59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/export-list"
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?
This pull request introduces major refactoring and feature changes, focusing on removing unused functionality, simplifying the codebase, and improving maintainability.
TaskServiceabstraction and theTasksProvidertrait, along with their implementations and dependencies.ComputerStorageEnginetoComputerStorageand consolidated all storage-related methods into this module. Added a newexport_listmethod to generate markdown representations of lists and tasksExportfunctionality from the content view and moved it to a context menu item in the sidebar.Gets us closer to #34
Pull Request Overview
This PR refactors storage and service layers, removes unused abstractions, and adds an
export_listmethod with a context-menu export action.TaskServiceand related traits/modules.ComputerStorageEnginetoComputerStorage, consolidates storage methods, and addsexport_list.Content, moving it into a new sidebar context menu.Reviewed Changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 2 comments.
Show a summary per file
mod todoTasksProvidertraitTaskServiceimplementationexport_listcomputerservice modulemodelsandstorageComments suppressed due to low confidence (1)
src/core/storage.rs:31
application_idinstead of the full storage path. Change this tocreate_dir_all(storage.path())so the correct directory is created.@ -0,0 +1,194 @@use std::path::PathBuf;The doc comment states that
newreturnsNone, but the signature returnsSelfand panics on failure. Update the documentation to accurately describe that it will panic on error rather than return anOption.[nitpick] Using
expecthere will panic the application on directory creation failure. Consider returning aResultor handling the error gracefully to avoid unexpected panics in production.@ -0,0 +44,4 @@}pub fn settings() -> Settings {Settings::default()Looks like this is not intended ? The app just always fail.
@ -0,0 +44,4 @@}pub fn settings() -> Settings {Settings::default()Yeah, I'm fixing it + another big change.
@ -0,0 +44,4 @@}pub fn settings() -> Settings {Settings::default()Just sent a fix to main