feat: add support for Telegram multi-chat data exports #134
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add automatic format detection for both single-chat and data exports - Extend TypeScript definitions for multi-chat export structure - Implement parseChatObject method for unified chat processing - Add comprehensive tests for multi-chat format - Update documentation and README with usage information - Maintain full backward compatibility with existing single-chat exports Closes: Support for parsing Telegram Desktop data exports (all chats) in addition to single-chat exports. Both formats are automatically detected and processed consistently.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for parsing Telegram Desktop data exports (all chats) in addition to the existing single-chat export support. Both formats are automatically detected and processed with full backward compatibility.
Changes
Core Implementation
Testing
Documentation
Testing Results
Backward Compatibility
This change is fully backward compatible. Existing single-chat exports continue to work exactly as before with no changes required from users.