History

Drop em-dashes from new comments

Rhys Sullivan committed 3 months ago

Commit 159ece51 parent 293f45f2 files · +3 −3Browse files

Unified · Split

2 files
  1. packages/core/sdk/src/oauth-register-dynamic.test.ts +1 −1
  2. packages/core/sdk/src/oauth-service.ts +2 −2
packages/core/sdk/src/oauth-register-dynamic.test.ts+1−1
@@ -623,7 +623,7 @@ describe("oauth.registerDynamicClient", () => { · 622 unmodified lines
623623 );
624624
625625 // Regression: Mercury's authorization server vets `client_name` and rejects
626− // any value containing its own brand with `invalid_client_metadata` — which
626+ // any value containing its own brand with `invalid_client_metadata`, which
627627 // the auto-generated "Executor for Mercury MCP" always trips. The name is
628628 // cosmetic, so registration must retry once with the bare product name
629629 // instead of failing the connect.
packages/core/sdk/src/oauth-service.ts+2−2
@@ -899,11 +899,11 @@ export const makeOAuthService = (deps: OAuthServiceDeps): OAuthService => { · 898 unmodified lines
899899 );
900900 const information = yield* registerWithName(input.clientName).pipe(
901901 // Some authorization servers vet `client_name` (Mercury rejects any
902− // name containing its own brand — which the auto-generated
902+ // name containing its own brand, which the auto-generated
903903 // "Executor for <integration>" always trips). The name is cosmetic,
904904 // so on `invalid_client_metadata` retry ONCE with the bare product
905905 // name before surfacing the failure. Other metadata rejections reuse
906− // the same RFC error code, so the retry may be a wasted request — but
906+ // the same RFC error code, so the retry may be a wasted request, but
907907 // never masks the original failure: if the retry also fails, ITS
908908 // error surfaces (same code, server-authored description).
909909 Effect.catchIf(