-
Notifications
You must be signed in to change notification settings - Fork 0
Support configurable storage driver, register S3/Google connectors, remove debug prints, and add release readiness review #6
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
Merged
squeakycheese75
merged 3 commits into
main
from
codex/review-go-codebase-for-release-readiness
Apr 7, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| # Public Release Readiness Review (April 7, 2026) | ||
|
|
||
| Status: **Not ready** for a clean first open-source release without targeted cleanup. | ||
|
|
||
| ## Highest-priority concerns | ||
|
|
||
| 1. Public API/config mismatch (`runtime.New` ignores storage driver and always creates SQLite client). | ||
| 2. Declared connector types are broader than registered defaults (e.g. S3 declared but not registered). | ||
| 3. Internal-only operational details leak into runtime output (git connector prints filesystem paths and tree contents). | ||
| 4. Public package surface and naming are inconsistent (`model` + `configs` + `entities`, typos, mixed naming styles). | ||
| 5. Documentation lacks clear stability guarantees and API boundaries for external contributors. | ||
|
|
||
| ## Release-focused recommendations | ||
|
|
||
| - Tighten public API surface to only the packages intended for users (`pkg/runtime`, `model`, and stable config package). | ||
| - Ensure declared connector/plugin types and runtime registrations are aligned. | ||
| - Remove debug prints and commented-out blocks from runtime-facing paths. | ||
| - Publish an explicit support matrix (connectors, dataset types, auth modes, and production readiness). | ||
| - Add tests for public constructors and capability registration consistency. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| package entities | ||
| package model | ||
|
|
||
| import ( | ||
| "fmt" | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
By removing the second
DatasetTypeSQLregistration, SQL datasets now always useSQLiteDataPlugineven whenstorage.driver=postgres. That plugin infers booleans asINTEGER(internal/plugins/sqlite/plugin.go), but Postgres insert generation emitsTRUE/FALSEliterals (internal/db/postgres.go), which causes type-mismatch failures when ingesting SQL datasets containing boolean fields on Postgres-backed runtimes. This regression comes directly from dropping the Postgres plugin registration in defaults.Useful? React with 👍 / 👎.