Whatsapp mono module #1108
Merged
Whatsapp mono module #1108
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In accordance with the creator of the Whatsapp Call History modules @Vinceckert, I added his name, description, version,... to my modified all-in-one whatsapp module.
I fixed the var/ prefix that all whatsapp modules were looking for, causing issues (no result) if the dump/zip doesn't contain the var/ path level
I have some weird things in the whatsapp contact module results, but good chances that it will be related to my specific case.
I commented some unused imports and rewrite some parts with non necessary f-strings in other whatsapp modules
I had some issues too with the lib2to3 import in the Facebook module. Commenting the import reloved the issue.