Skip to content

chore: sync generated client with API - #57

Merged
leo-notte merged 1 commit into
mainfrom
chore/sync-staging-openapi-20260805
Aug 5, 2026
Merged

chore: sync generated client with API#57
leo-notte merged 1 commit into
mainfrom
chore/sync-staging-openapi-20260805

Conversation

@leo-notte

Copy link
Copy Markdown
Contributor

Summary

  • regenerate the Go API client from the current Notte OpenAPI schema
  • refresh generated session-start flags for managed-auth options

Verification

  • go test ./...
  • make check (run after commit)

@greptile-apps

greptile-apps Bot commented Aug 5, 2026

Copy link
Copy Markdown

Greptile Summary

This PR regenerates the Go API client from the current schema and exposes managed-auth controls on sessions start.

  • Adds managed-auth schemas, endpoints, request parameters, and response fields to the generated API client.
  • Adds repeatable --auth-ids and optional --wait-for-authentication session-start flags.
  • Adds generated support for system-session filtering and uploaded-file downloads.

Confidence Score: 4/5

The PR appears safe to merge, with the non-blocking exception that the new managed-auth flag mappings lack regression tests.

The generated client remains compatible with checked callers, and the new request builder preserves omitted optional values correctly; only test coverage for the newly exposed flags is missing.

Files Needing Attention: internal/cmd/sessionstart_flags.gen.go

Important Files Changed

Filename Overview
internal/api/client.gen.go Regenerates the API surface with managed-auth models and operations plus additive schema updates; checked client operation signatures remain compatible with existing callers.
internal/cmd/sessionstart_flags.gen.go Correctly maps the two new managed-auth flags into optional API fields, but no tests cover their serialization semantics.

Fix All in Codex

Prompt To Fix All With AI
### Issue 1
internal/cmd/sessionstart_flags.gen.go:99-104
**Managed-auth flags lack coverage**

The new `AuthIds` and `WaitForAuthentication` mappings have no tests confirming repeatable ID handling or the distinction between an omitted boolean and explicit false, leaving future generator regressions in these request semantics undetected.
- Add a comment if the PR does n... ([source](https://app.greptile.com/review/custom-context?memory=instruction-0))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "chore: sync generated client with API" | Re-trigger Greptile

@leo-notte
leo-notte merged commit dc28150 into main Aug 5, 2026
4 checks passed
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