feat(kiota): tests wave — all 13 tests_* resources bind fluent - #110
Merged
Conversation
The largest wave of the parity plan, and the first to need nothing from the emitter: thirteen resources ported as pure blueprint data through the SDK-resolved port tooling, 1030 bindings verifying against the generated SDK on the first complete run. The two shapes that looked like problems were not: alert_rules and custom_headers -- where kiota's request and response models genuinely disagree, or where the model is a free-form AdditionalData holder -- are dropped attributes in the resty curation, never rendered, and the port now leaves dropped attributes' wires untouched as the documentation they are. Every recorded tests_* subject reproduces its facts from the shared cassettes; both pilots' drift checks hold and all three test suites pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Why
PR 3 of 4 in the kiota/resty parity plan (#107 foundations, #108 admin wave, #109 live fixes — acceptance run #6 green). This is the largest wave: all thirteen
tests_*resources join the kiota pilot, taking it from 7 to 20 resources and from 174 to 1030 verified bindings.What
Pure blueprint porting — the first wave to need no emitter, converter, or SDK changes at all. The SDK-resolved port tooling (builder-chain walking from path templates, direction-aware accessor resolution against request vs response models) carried every resource:
bindings checkpassed 1030/1030 on the first complete run.Two apparent problem shapes dissolved on inspection:
alert_rules— kiota's request model wants[]stringof rule IDs where the response returns full objects;custom_headers— free-formAdditionalDataholder models. Both are dropped attributes in the resty curation (never rendered), so nothing binds to them. The port tool now skips dropped attributes, leaving their wires untouched as documentation.Verification
bindings check: ✅ 1030/1030 (20 resources, 2 data sources, 1 list facet, 1 action, 1 ephemeral)probe verify: every recordedtests_*subject reproduces its facts from the shared cassettes (10 of 13 have recordings, same coverage as resty); exit 0provider generate -check: 0 drift on both pilotsAfter merge: dispatch
go | Acceptance tests (kiota)(the tests wave is acc-gated the same way as resty's). Then PR 4 — alert_rule, dashboard, dashboard_filter — completes parity.🤖 Generated with Claude Code