Skip to content

Nullify replyToMessageId if it's an empty string#509

Merged
mrashed-dev merged 1 commit intomainfrom
TW-2381-gh-484-node-undefined-reply-to-message-id-results-in-empty-string
Nov 28, 2023
Merged

Nullify replyToMessageId if it's an empty string#509
mrashed-dev merged 1 commit intomainfrom
TW-2381-gh-484-node-undefined-reply-to-message-id-results-in-empty-string

Conversation

@mrashed-dev
Copy link
Copy Markdown
Contributor

@mrashed-dev mrashed-dev commented Nov 28, 2023

Description

This PR closes #484.

License

I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@mrashed-dev mrashed-dev merged commit 9747bfa into main Nov 28, 2023
@mrashed-dev mrashed-dev deleted the TW-2381-gh-484-node-undefined-reply-to-message-id-results-in-empty-string branch November 28, 2023 16:56
@mrashed-dev mrashed-dev mentioned this pull request Nov 28, 2023
mrashed-dev added a commit that referenced this pull request Nov 29, 2023
# Changelog
* Add support for logging (#508, #456)
* Nullify replyToMessageId is an empty string (#484, #509)
* Nullify visibility if visibility is an empty string (#507, #470)
* Fix numbers defaulting to 0 instead of null (#469)
* Fix parsing of Number arrays (#503, #502)
* Fix configured timeout not being used (#506, #489)
* Bump `node-fetch` dependency from 2.6.1 to 2.6.12 (#504, #496)
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.

undefined replyToMessageId results in empty string

2 participants