Remove comments

Author: razor-x

src/lib/seam-http-request.ts

@@ -23,11 +23,6 @@ interface SeamHttpRequestConfig<TResponseKey> {
   readonly responseKey: TResponseKey
   readonly options?: Pick<SeamHttpRequestOptions, 'waitForActionAttempt'>
   readonly actionAttempts?: ActionAttemptsClient
-  /**
-   * The parameters as given to the endpoint method, validated when the request
-   * is made. Held separately from `body` and `params` so that `undefined` and
-   * `null` stay distinguishable from an endpoint that takes no parameters.
-   */
   readonly parameters?: unknown
   readonly hasRequiredParameters?: boolean
   readonly requiredParameterNames?: readonly string[]
@@ -131,11 +126,6 @@ export class SeamHttpRequest<
   }
 
   async fetchResponse(): Promise<TResponse> {
-    // Validated here, not when the endpoint method builds this request:
-    // requests are values, and callers may build one well before deciding to
-    // send it. Reporting a bad parameter at build time surprises anyone who
-    // constructs a request up front, e.g. to derive a cache key from it, and
-    // then only sends it once the data it needs is available.
     assertValidRequestParameters(
       this.#config.parameters,
       this.pathname,

test/seam/connect/request-parameters.test.ts

@@ -106,9 +106,6 @@ test('endpoint accepts required parameters', (t) => {
 })
 
 test('endpoint defers parameter validation until the request is made', (t) => {
-  // A request is a value: callers may build one before deciding to send it, or
-  // to derive a cache key from it, so building must not throw on parameters
-  // that are not ready yet.
   t.notThrows(() => {
     // @ts-expect-error Verify an invalid request still builds.
     seam.devices.get({ device_id: undefined })