feat: migrate all resources to the real SuperOps GraphQL schema#9
Merged
Conversation
Completes the v2 migration started for assets (#8). Every remaining resource queried an assumed schema the real SuperOps API rejects. - Migrate tickets, clients, sites, alerts, contracts, technicians and knowledge-base to SuperOps' real schema: `input:`-argument queries, page-based pagination (Page<T>/PageParams), and corrected type/field names. Each resource + its types, mocks and integration tests were rewritten. - Remove runbooks, patches, remote-sessions and reports — built entirely on the assumed schema with no standalone SuperOps API equivalent (see SCHEMA.md). - Split test mocks into per-resource files under tests/mocks/handlers/. - Update SCHEMA.md and the README to the real API surface. Fidelity caveat: corrected from public docs, not live introspection; unverified input-type fields are flagged in source. See SCHEMA.md and #7. BREAKING CHANGE: all resource APIs changed to match SuperOps' real GraphQL schema; list methods return page-based Page<T>; the runbooks, patches, remoteSessions and reports resources were removed.
github-actions Bot
pushed a commit
that referenced
this pull request
May 21, 2026
# [3.0.0](v2.0.0...v3.0.0) (2026-05-21) ### Features * migrate all resources to the real SuperOps GraphQL schema ([#9](#9)) ([193786c](193786c)), closes [#7](#7) ### BREAKING CHANGES * all resource APIs changed to match SuperOps' real GraphQL schema; list methods return page-based Page<T>; the runbooks, patches, remoteSessions and reports resources were removed.
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.
Completes the schema migration started for
assetsin #8. Closes #7.What
Every resource other than
assetsstill queried the imaginary schema and would fail against the real SuperOps API. This migrates the rest and prunes the fictional ones.Migrated to SuperOps' real schema (
input:-argument queries, page-based pagination, corrected field names) — resource, types, mocks and integration tests rewritten for each:tickets,clients,sites,alerts,contracts,technicians,knowledgeBase.Removed — built entirely on the assumed schema, no standalone SuperOps API equivalent:
runbooks,patches,remoteSessions,reports. (Patch/script data exists only as asset-scoped operations; may return later if scoped properly — noted inSCHEMA.md.)Also: test mocks split into per-resource files under
tests/mocks/handlers/;SCHEMA.mdandREADME.mdupdated to the real API surface.How it was done
Seven parallel agents, one per resource, each owning disjoint files (
resources/X.ts,types/X.ts,tests/mocks/handlers/X.ts,tests/integration/X.test.ts), all following the mergedassetsresource as the reference pattern.Corrected from SuperOps' public docs, not live introspection (no API tenant was available — see #7). Query names, the
input:convention and object field names are well-corroborated; input-type field names are best-effort and flagged with// NOTE: unverified against live APIcomments. They should be confirmed against a live tenant.Verification
npm ci+ lint + typecheck + build + test + smoke test all green — 157 tests pass across 13 files.Release
Breaking change → semantic-release will cut v3.0.0 on merge. As with #8, I did not auto-merge — your call on review and merge timing.