-
Notifications
You must be signed in to change notification settings - Fork 452
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
Fix invalid JSON in /version endpoint response #538
Conversation
I have signed the CLA! |
Hi @miry! 👋 This seems like a small but nice fix to have in here. Let me know if I can do anything to expedite this 😊 |
cc: @abecevello |
This should work, running this playground shows the difference between the two string structures. Once CI passes, I'll also throw an approval on this 👍 |
@whatyouhide I've run the tests and it looks like |
Ah, yes. Sorry, I didn't even run tests locally cause I don't work in Go and had nothing set up for it. I took the laziest approach 😅 Anyways, I pushed a commit that should fix the test 🤞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
@whatyouhide thanks for the fix. I've merged it and I'll see about doing a release that includes this soon. |
The
/version
endpoint returns invalid JSON, because the\n
character at the end of the response is escaped by the backticks. This PR should fix that. I’m no Go expert, so I’m just winging this 🙃