-
Notifications
You must be signed in to change notification settings - Fork 2
Multi go module setup #2
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
Conversation
f690bdc to
3c24a99
Compare
rcambrj
left a comment
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.
Great work, only minor comments.
| **Controller Changes** (`pkg/{module}/controller/`): | ||
| - Run tests in the specific module: `cd pkg/resource-handler && go test ./...` | ||
| - Integration tests catch reconciliation bugs early | ||
| - Use `make run` for quick iteration (no docker build needed) |
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.
I realise that this line is unchanged - just pointing out that we should remember to create a Makefile with a run target :D
This introduces the multi Go module setup, where each module can have separate dependencies.
For local development, you can ensure LSP checks at one go.mod by opening at the module root directory, or use
go.workandgo workspacesetup to allow opening up from the repository root. There is some mention about Go workspace usage included in the document as well.NOTE: I have added test impl ofmain.go, as well asgo.workwhich is only meant to be used locally. This is just to demonstrate how we can handle the configuration, and that commit should be removed before this can be merged.This has been removed.