feat(go): Add context support to all requests

[mehmetaligok]

🧭 What and Why

🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-696

We need to provide a way to accept users' context while respecting general conventions in Go.

Changes included:

• Wrapper functions with a WithContext suffix added for all API methods to comply with the general DX standards.
  Ex:

// CreateAuthentication wraps CreateAuthenticationWithContext using context.Background.
func (c *APIClient) CreateAuthentication(r ApiCreateAuthenticationRequest, opts ...Option) (*AuthenticationCreateResponse, error) {
	return c.CreateAuthenticationWithContext(context.Background(), r, opts...)
}

// @return AuthenticationCreateResponse
func (c *APIClient) CreateAuthenticationWithContext(ctx context.Context, r ApiCreateAuthenticationRequest, opts ...Option) (*AuthenticationCreateResponse, error) {
.
.
.
// actual implementation
}

• Playground example added to show context usage.

🧪 Test

Code generation and CI pipeline should be enough.

[netlify]

✅ Deploy Preview for api-clients-automation ready!

Name	Link
🔨 Latest commit	7c5dc94
🔍 Latest deploy log	https://app.netlify.com/sites/api-clients-automation/deploys/645a3d3e7b1b99000746be02
😎 Deploy Preview	https://deploy-preview-1527--api-clients-automation.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[algolia-bot]

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.
You can still access the code generated on main via this commit.

[millotp]

love it ! just a suggestion

[millotp]

should you also add the description to this method ? I guess people will use this one first, I think it's okay to have duplicated doc in generated code, wdyt ?

[mehmetaligok]

I saw this general convention on other popular packages. But your suggestion is also valid.

However, if you don't mind, is it okay to update these docs in another PR? Because, if you check you can see the actual method doesn't have a proper doc already. Most of them just say something like // @return AuthenticationCreateResponse.
I already have a ticket in the backlog to generate proper doc comments for the API functions to guide users. I think this may belong there as well.

[millotp]

sure if there is a ticket no problem !

[millotp]

gg !

[millotp]

Hey, can you wait for #1534 to be merged before merging this one pls ? Once a release PR is open we can't merge anything in between otherwise it breaks the release process

[mehmetaligok]

Hey, can you wait for #1534 to be merged before merging this one pls ? Once a release PR is open we can't merge anything in between otherwise it breaks the release process

@millotp sure no worries. I opened auto-merge on my other PR without noticing the release PR. Sorry if that blocked you :(

[millotp]

no worries the process is a bit messy, it was just to let you know :)