@mnafees, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction.

@mnafees, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed.

@mnafees, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement. Reject reason:

Can you please provide a full address ?

@mnafees, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed.

@mnafees, VMware has approved your signed contributor license agreement.

Hello @mnafees ,

Thank you for this amazing contribution! I added two minor comments. The code looks great and all the examples work perfectly.

Apart from the examples, we should include a new documentation page for Go. It's not a blocker for merging this, so we can work on it in a separate PR. If it's fine for you, I would add a note in that documentation page mentioning you as the original author of the Go kit.

Thank you! 🎉

I am going to add code comments as well as the docs for the new Go support kit and update the PR accordingly :)

Hey @mnafees!

This is just a check on the status of this PR :). I believe the current Go kit is in a great shape to included in the project.

If you are more busy lately, I can do a final review, merge it and create an issue to work on the documentation in a separate PR. If you prefer to complete the documentation on this PR, feel free to add it too.

No rush for it. I just wanted to to do a check since the latest comment was from a few days ago.

Thanks!

Hi @Angelmmiguel, apologies for being AWOL for a while. I got busy with other work. I am updating the PR with the docs. I also went ahead and chose to use the sjson library as suggested by you. Will update with a new comment once the PR is ready for your re-review. Thank you for the patience!

Hi @Angelmmiguel, apologies for being AWOL for a while. I got busy with other work. I am updating the PR with the docs. I also went ahead and chose to use the sjson library as suggested by you. Will update with a new comment once the PR is ready for your re-review. Thank you for the patience!

Hello @mnafees! No worries, you don't need to apologize 😄. I regularly check open PRs in case I can help on anything. Thank you very much for your contribution! 👏

@Angelmmiguel I have updated the PR with all of my changes to the documentation :)

Btw, no worries about the issue on the CI. It's a flaky test I need to fix in main and it's not related to your changes. I will retry it after other builds finish.

Awesome contribution @mnafees! 🚀