Skip to content

Clarify live API conformance gap in Future Direction#23

Merged
jpr5 merged 2 commits intomainfrom
docs/future-direction-fix
Mar 11, 2026
Merged

Clarify live API conformance gap in Future Direction#23
jpr5 merged 2 commits intomainfrom
docs/future-direction-fix

Conversation

@jpr5
Copy link
Contributor

@jpr5 jpr5 commented Mar 11, 2026

Summary

  • Replaces misleading "E2E SDK tests" bullet with accurate description: we have api-conformance tests that validate response format structure, but the real gap is tests that run against actual LLM APIs (gated behind API keys) to catch format drift as providers evolve

Test plan

  • Docs-only change, no code impact

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 11, 2026

Open in StackBlitz

npm i https://pkg.pr.new/CopilotKit/llmock/@copilotkit/llmock@23

commit: 188ede4

Copy link

@claude claude bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — docs-only clarification of a Future Direction bullet.

Extended reasoning...

Overview

This PR changes a single line in README.md under the Future Direction > Testing section. It replaces the old "E2E SDK tests" bullet with a more accurate description: the project has api-conformance tests that validate response format structure, but the real gap is tests that run against actual LLM provider APIs (gated behind API keys) to catch format drift.

Security risks

None. This is a documentation-only change with no code impact.

Level of scrutiny

Minimal scrutiny required. This is a one-line wording change in a readme file with no functional impact on the codebase.

Other factors

No bugs were found. No outstanding reviewer comments. The change is self-contained, accurate based on the project structure, and improves clarity over the previous bullet point.

@jpr5 jpr5 merged commit b625bfb into main Mar 11, 2026
8 checks passed
@jpr5 jpr5 deleted the docs/future-direction-fix branch March 11, 2026 21:41
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