-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make history persistent #40
Conversation
Create 'load' function to load the conversation in the archive file to history and call it when application is starting
Add Automatically load the last saved chat into history.
- Load chats in the data directory to history - When a new chat is created, save in a file - Remove default archive file - Remove Save history feature (CTRL-S)
update README with the persistent history feature
src/history.rs
Outdated
Ok(_) => { | ||
let notif = Notification::new( | ||
format!("Chat saved to `{}` file", archive_file_name), | ||
format!("Chat saved to `{}` file", file_path.display()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a message like Chat Saved
is enough, no need to mention the file
src/history.rs
Outdated
format!( | ||
"Chat loaded in history from `{:?}` files", | ||
directory_path.display() | ||
), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, just History loaded
is enough as a message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to remove the message from help.rs
as well
Great job 👏 There is few things we can add, maybe in other PR:
What do you think ? |
Yes it's a good idea, i created a new issue (#41 ) for this features, if anyone want to make a new PR |
I will merge this one and we can continue on other PRs |
After review of the pull request #39, add feature of the issue #33
Changes: