refactor(render): one module, one version — fold webkit + php into dappco.re/go/render#40
Conversation
…ppco.re/go/render display/webkit and engine/php carried their own go.mod, making them nested modules carved out of the render package tree — so `dappco.re/go/render/display/webkit` was not importable at render's version (no separate tag ever cut). go-render is ONE repo, ONE version: delete the nested go.mod/go.sum, fold their deps (wails/v3, webview, frankenphp, mercure, otel, ...) into go/go.mod, drop the two nested `use` entries from go.work. display/webkit and engine/php are now packages of dappco.re/go/render, resolvable at the render tag. Consumers `go get dappco.re/go/render@vX` and import the webkit/php packages directly — no per-subdir tag. Gate: GOWORK=off go build ./... (Success, webkit cgo compiled) · go vet ./... clean. Co-Authored-By: Virgil <virgil@lethean.io>
|
Warning Review limit reached
Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (3)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
1 participant
display/webkitandengine/phpeach carried their owngo.mod, making them nested modules carved out of the render package tree. Result:dappco.re/go/render/display/webkitwas not importable at render's version (render@v0.18.0can't see a nested module, and no per-subdir tag was ever cut) — which blocked the desktop app's migration onto webkit.go-render is one repo, one version. This deletes the nested
go.mod/go.sumand folds their deps (wails/v3, webview, frankenphp, mercure, otel, …) into the singlego/go.mod; drops the two nesteduseentries fromgo.work.display/webkitandengine/phpare now packages ofdappco.re/go/render, resolvable at the render tag. Consumersgo get dappco.re/go/render@vXand import the packages directly — no per-subdir tag ever again.Gate:
GOWORK=off go build ./...→ Success (webkit cgo compiled) ·go vet ./...clean.🤖 Generated with Claude Code
Co-Authored-By: Virgil virgil@lethean.io