feat: add conformance Tests for SEP-2549: TTL for List Results#275
Merged
Conversation
commit: |
9 tasks
CaitieM20
changed the title
felixweinberger
previously approved these changes
May 19, 2026
Collaborator
felixweinberger
left a comment
felixweinberger
left a comment
There was a problem hiding this comment.
LGTM overall, just needs a rebase / CI fix I think.
Could consider adding a client scenario to specifically catch polling as a WARNING (rather than a FAILURE) to discourage SDKs from writing polling as a default which we seem to want to deliberately avoid, but wouldn't block on it.
panyam
reviewed
May 19, 2026
panyam
reviewed
May 19, 2026
panyam
reviewed
May 19, 2026
panyam
reviewed
May 19, 2026
tarekgh
reviewed
May 20, 2026
tarekgh
reviewed
May 20, 2026
… this PR was lint noise" This reverts commit b5fe149.
pcarleton
added a commit
that referenced
this pull request
May 22, 2026
* chore: refresh SEP traceability manifest (typescript-sdk@main) Regenerated from a client+server suite run against typescript-sdk@5fc42e9be115 following the recipe in .github/workflows/traceability.yml. New entries since the last refresh (typescript-sdk@22595b96): - SEP-2322 (MRTR, #188): 17 tested, 0 untested, 16 excluded, 3 untracked - SEP-2549 (TTL for list results, #275): 7 tested, 0 untested, 13 excluded - SEP-2260: 12 excluded rows, no checks - SEP-2207: yaml rows added since the last refresh now appear (1 tested, 1 untested: sep-2207-server-no-offline-access) No previously-tested requirement regressed. * Exclude sep-2207 server offline_access guidance until RS auth scenarios exist sep-2207-server-no-offline-access was declared in the yaml but no scenario emits it, so it surfaced as the only untested requirement in the refreshed manifest. The check needs to probe the SDK server's Protected Resource Metadata scopes_supported and WWW-Authenticate challenge scope, and the server suite does not yet exercise the SDK server as an OAuth protected resource at all. Mark the requirement excluded with a pointer to #116 (server-side authorization baseline) rather than leaving it as a permanently-untested row; revisit when server-side authorization scenarios land.
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
5 participants
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.
Conformance Tests for SEP-2549: TTL for List Results
Motivation and Context
Conformance tests for new feature
How Has This Been Tested?
Local tests related to this change pass, there is an existing test in main related to SEP-2164 that is failing, but unrelated to this change.
Breaking Changes
no
Types of changes
Checklist