Removed nested message stringify #393
Merged
+28
−27
Conversation
This file contains 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
Also discovered the toJSON method, so _build is no longer needed
|
Visit the preview URL for this PR (updated for commit f3a5a74): https://whatsappapijs--pr393-no-stringify-op7gzrvq.web.app (expires Tue, 07 Jan 2025 16:30:38 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 80a8dc4ceea5c783aae1d47b75797ee5b6c2f4be |
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.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
npm run testand lint the project withnpm run lintandnpm run prettierWith this new structure, ClientMessageRequest is fully typed and will probably be faster to send messages as JSON.stringify is called less times.
Closes #374