Skip to content
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

feat: add chat history backup and restore functionality #871

Open
wants to merge 19 commits into
base: main
Choose a base branch
from

Conversation

sidbetatester
Copy link

This PR adds chat history backup and restore functionality, continuing the work from #280.

Changes include:

  • Enhanced chat import with support for multiple formats:
    • Standard Bolt format
    • Chrome extension IndexedDB backup format
    • History array format
  • Improved validation and error handling
  • Added user feedback via toast notifications
  • Updated README to reflect the new feature

Note: After the #280 commits, the structure of bolt has significantly changed, so in this commit, I only introduced what you missed including from my previous commit and must not have any conflicts.

Previous feedback addressed:

  1. Fixed TypeScript issues
  2. Improved error handling and validation
  3. Added proper success messages
  4. Cleaned up code organization

Reference: This continues the work from #280 which was accidentally closed during branch reorganization.
#280

@sidbetatester sidbetatester changed the title feat: Add chat history backup and restore functionality feat: add chat history backup and restore functionality Dec 22, 2024
@sidbetatester
Copy link
Author

Hi Anirban @thecodacus
I cleaned up the code to match latest version, we should not have any conflicts now. Can you verify and approve.

@thecodacus
Copy link
Collaborator

Hi Anirban @thecodacus I cleaned up the code to match latest version, we should not have any conflicts now. Can you verify and approve.

I have added my reviews. I just noticed that you are using your main branch to raise PR, Please read the contribution guidelines here , and use a feature branch for the PR. else any changes to your main will automatically be reflected to this PR which can be problematic.

@sidbetatester
Copy link
Author

Hi Anirban @thecodacus I cleaned up the code to match latest version, we should not have any conflicts now. Can you verify and approve.

I have added my reviews. I just noticed that you are using your main branch to raise PR, Please read the contribution guidelines here , and use a feature branch for the PR. else any changes to your main will automatically be reflected to this PR which can be problematic.

thank you, acknowledged, I did follow the CONTRIBUTING.md the first time, should have remembered to do that same. I was using windsurf for my edits and commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants