fix: set correct Content-Type#228
Merged
thjaeckle merged 1 commit intoeclipse-ditto:masterfrom Mar 12, 2024
Merged
Conversation
Contributor
Author
|
@thjaeckle Do you have a timeline for the next release with this fix? |
Member
|
@PJGitLan oh, it should have been in 3.5.4 - but I see we did not publish that to npm .. |
Contributor
Author
No problem and thank you! |
Member
|
@PJGitLan 3.5.4 was published on npm |
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
2 participants
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.
Content-Type was not set correctly for postCount() and postSearch()