Regenerate from v1.7.2+ — drop three unreachable endpoints, add SubgraphLimits - #171
Merged
Merged
Conversation
The API removed three routes that had shipped shadowed: a literal segment registered after a param-segment sibling never wins, so `getSubgraphQuota`, `batchProcessQueries` and `recommendOperator` could only ever 404. Removing them breaks symbol resolution, never behavior — no integration could have been working against them. `getSubgraphQuota`'s data moves to `getGraphLimits`, which gains a `subgraphs` block (`SubgraphLimits`) alongside `documents`. The API now computes `approaching_limit` rather than leaving callers to derive it. Also picks up backend drift since the last generation: event-block payload drift, stranded-obligation reporting on the fiscal calendar, and the promote-obligations request/response shapes.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Regenerated against RoboFinSystems/robosystems#1073.
Removed — three endpoints that could only ever 404
getSubgraphQuota,batchProcessQueries,recommendOperator. All three shipped shadowed on the API: a literal path segment registered after a param-segment sibling never wins, because matching stops at the first route whose path matches and params are validated only afterward. They were documented in the OpenAPI spec and generated into this client, but no call to any of them has ever returned a 200.That is what makes this cheap. Removal breaks symbol resolution, never behavior — no integrator can hold a working integration against a permanent 404. Retracting is the expensive direction only when there is working behavior to protect, and there is none here.
Gone with them:
BatchOperatorRequest,BatchOperatorResponse,OperatorRecommendation,OperatorRecommendationRequest,OperatorRecommendationRequestContextType0,OperatorRecommendationResponse,SubgraphQuotaResponse.Added —
SubgraphLimitsongetGraphLimitsgetSubgraphQuota's data moves ontoGraphLimitsResponse.subgraphs, next todocuments, which it mirrors:current_count/max_allowed/remaining/approaching_limit. Populated for parent user graphs; absent for shared repositories and subgraphs.The API now computes
approaching_limitrather than leaving callers to derive it, and callers that already fetch limits get the count without a second round-trip.total_size_mb/max_size_mbare not carried over — they were an unimplemented TODO on the old response that always returnedNone.Also picked up — drift since the last generation
Not part of the endpoint change; these are additive backend fields this regen catches up on:
EventBlockEnvelopepayload-drift field and theeventBlocksfilter argFiscalCalendarstranded-obligation reporting (strandedObligationCount,strandedObligationSample, thestranded_obligationsblocker code) andClosePeriodrequest/response fieldsPromoteObligationsrequest/response shapesBackfillPlanHistoryoperationschema.graphqlrefreshed accordingly (2434 → 2445 lines), so the hermetic drift gate stays clean.Verification
just test-allgreen — 518 passed, 17 skipped; ruff check + format clean; basedpyright 0 errors.Version
Left at its current value for you to set on publish. The behavioral case for a patch/minor is above; it is still a public-symbol removal against the integration template's
>=1,<2pin, so the call is yours.Merge after RoboFinSystems/robosystems#1073.