ZekiLiu opened a new pull request, #937:
URL: https://github.com/apache/incubator-graphar/pull/937
### Reason for this PR
This PR starts the Go SDK work tracked by #828.
The Go SDK needs a standalone module layout and CI/tooling foundation before
the actual GraphAr metadata APIs are added. Keeping this bootstrap change
small
also makes the follow-up info implementation easier to review as a stacked
PR.
Refs #828.
### What changes are included in this PR?
This PR adds the initial Go SDK scaffold:
- create the `go/graphar` Go module
- add the umbrella `graphar` package documentation
- add Go development targets for formatting, vetting, linting, testing,
coverage, and license checks
- add a GitHub Actions workflow for Go CI when files under `go/**` change
- update license configuration for Go source files
This PR intentionally does not add the `types` or `info` package
implementation
yet. Those APIs are planned for the stacked follow-up PR.
### Are these changes tested?
The intended local and CI checks are:
- `cd go/graphar && go mod tidy`
- `cd go/graphar && go test ./...`
- `cd go/graphar && make ci`
- `pre-commit run --files .github/workflows/go.yaml go/README.md
go/graphar/.golangci.yml go/graphar/Makefile go/graphar/doc.go
go/graphar/go.mod go/graphar/go.sum`
### Are there any user-facing changes?
Yes. This introduces the new Go SDK module directory and its README, but it
does
not change any existing GraphAr API behavior.
## Checklist
- [x] I have performed a self-review of my own code.
- [x] I have formatted my own code using `make cpplint` before submitting
when changed files are in the `cpp` directory. (Not applicable: this PR does
not change files in the `cpp` directory.)
- [x] I have performed `pre-commit run` before commit the changed files.
- [x] I have added tests to prove my changes are effective. (CI/tooling
bootstrap is covered by the Go workflow and module checks listed above;
implementation tests are added in the stacked follow-up PR.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]