Separate the Go client into its own `@netlify/go-sdk` repository
Open
Nobody has claimed this yet.
enhancement
go
- Dominant language
- Go
- Stars
- 323
- Forks
- 133
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 2
Description
It seems to me the Go-related code should be abstracted to its own @netlify/go-sdk repository.
This would make both the Go client and the OpenAPI code easier to work with. This would also:
- separate concerns
- speed up CI
However Go imports might be broken when doing so, so this needs to be done carefully.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the Go-related code and OpenAPI code in the repository, then trace the Go imports that could break during extraction. Define the repository boundary and CI changes needed for the separation; done means the Go client is independently maintained with working imports and the existing API behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, openapi
- Domain
- api, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100