Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support parsing messages with missing space after colon #29

Merged
merged 2 commits into from
Jun 29, 2016

Conversation

clue
Copy link
Owner

@clue clue commented Jun 29, 2016

This makes the parser more robust to some malformed legacy messages, such as in #28.

This builds on top of #28.

@bonan
Copy link
Contributor

bonan commented Jun 29, 2016

I've pulled this PR and did a quick test with one of my applications, it seems to work as intended.
The problem with missing space after colon ( #28 and #29 ) is no longer an issue.

@clue
Copy link
Owner Author

clue commented Jun 29, 2016

Thanks for the confirmation @bonan, let's get this in :shipit:

@clue clue merged commit 4f37fef into clue:master Jun 29, 2016
@clue clue deleted the parse-without-space branch June 29, 2016 11:11
@clue clue mentioned this pull request Nov 1, 2016
@avbdr
Copy link

avbdr commented Nov 1, 2016

awesome. thanks.

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.

3 participants