feat(Message): add 'failIfNotExists' to ClientOptions #6038
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
iCrawl
approved these changes
Jul 4, 2021
kyranet
approved these changes
Jul 4, 2021
vladfrangu
approved these changes
Jul 4, 2021
SpaceEEC
approved these changes
Jul 5, 2021
|
This needs a rebase. |
iCrawl
reviewed
Jul 5, 2021
Co-authored-by: Noel <buechler.noel@outlook.com>
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 describe the changes this PR makes and why it should be merged:
This PR adds
failIfNotExiststo ClientOptions. The reason why is: some devs may not want errors when the referenced message does not exist. Setting this option to false to every ReplyMessageOptions seems like a poor idea, easy to forget, so I added this option to ClientOptions.Status and versioning classification: