Skip to content

feature(op): Export Marshal/UnmarshalToAny, style compliance (Phase 4) - #212

Merged
David-Noble-at-work merged 1 commit into
developfrom
feature/shared-provider-receivers
Mar 12, 2026
Merged

David-Noble-at-work merged 1 commit into
developfrom
feature/shared-provider-receivers

Conversation

@David-Noble-at-work

Copy link
Copy Markdown
Contributor

Summary

  • Export marshal → Marshal and unmarshalToAny → UnmarshalToAny in pkg/op/starvalue_marshal.go so noblefactor-ops can replace its parallel starlarkToGo/goToStarlark implementations
  • Update all internal call sites (pkg/op/output.go, pkg/op/receiver_reflect.go, test files)
  • Add §4-compliant doc comments (Parameters/Returns) to all exported methods and unexported helpers across all 14 production files touched in Phases 1-4
  • Add doc comments to unexported struct types (receiverEntry, typeInfo, fieldInfo)

Part of the shared-provider-receivers plan. Phases 1-3 merged in #210, #211. Phase 5 follows.

Test plan

  • make build passes
  • make test passes (all packages)
  • CI passes

Export marshal as Marshal and unmarshalToAny as UnmarshalToAny in
pkg/op/starvalue_marshal.go for use by noblefactor-ops.

Update all internal call sites to use exported names. Add
Parameters/Returns doc comments to all exported and unexported helpers
across 14 production files touched in Phases 1-4. Add doc comments to
unexported struct types (receiverEntry, typeInfo, fieldInfo). Fix sort
order: UnmarshalToAny (exported) before unmarshal (unexported).

Phase 4 of shared-provider-receivers plan.
@David-Noble-at-work
David-Noble-at-work merged commit d2c9193 into develop Mar 12, 2026
2 checks passed
@David-Noble-at-work
David-Noble-at-work deleted the feature/shared-provider-receivers branch March 12, 2026 19:15
David-Noble-at-work added a commit that referenced this pull request Jul 28, 2026
… the stated mechanism (#302)

The #300 live proof cut both ways: the --admin merge worked (site PR
#211, merged by the app with checks pending and zero reviews), then the
very next run's merge died on a GitHub 502 and stranded site PR #212
open with green checks. All three sync merges (docs, install script,
registry knowledge) now run in a bounded retry loop — 5 attempts,
10/20/30/40s backoff — that consults the PR state before retrying,
since a 5xx can arrive after the merge landed server-side.

The registry merge also gains --admin: devlore-registry develop sits
under the same org ruleset, and the plain merge already failed live —
registry PR #69 was app-created, its Knowledge Extract run failed on
the merge step, and the PR was merged by hand two minutes later.

Comments corrected: --admin disarms gh's client-side merge-state veto;
the server-side entitlement is the automation app's "always" bypass on
the org ruleset, not repository admin rights. Correction noted in
docs/plans/ci-admin-merge-sync-prs.md.

Workflow-only change; the live proof is the next sync chain run. Plan:
docs/plans/ci-sync-merge-retry.md.

Co-authored-by: David Noble <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant