HttpApiBuilder: URL parameters are now automatically converted to arr…

[gcanti]

…ays when needed, closes #4442

Example

import {
  HttpApi,
  HttpApiBuilder,
  HttpApiEndpoint,
  HttpApiGroup,
  HttpMiddleware,
  HttpServer
} from "@effect/platform"
import { NodeHttpServer, NodeRuntime } from "@effect/platform-node"
import { Effect, Layer, Schema } from "effect"
import { createServer } from "node:http"

const api = HttpApi.make("api").add(
  HttpApiGroup.make("group").add(
    HttpApiEndpoint.get("get", "/")
      .addSuccess(Schema.String)
      .setUrlParams(
        Schema.Struct({
          param: Schema.NonEmptyArray(Schema.String)
        })
      )
  )
)

const usersGroupLive = HttpApiBuilder.group(api, "group", (handlers) =>
  handlers.handle("get", (req) =>
    Effect.succeed(req.urlParams.param.join(", "))
  )
)

const MyApiLive = HttpApiBuilder.api(api).pipe(Layer.provide(usersGroupLive))

const HttpLive = HttpApiBuilder.serve(HttpMiddleware.logger).pipe(
  Layer.provide(MyApiLive),
  HttpServer.withLogAddress,
  Layer.provide(NodeHttpServer.layer(createServer, { port: 3000 }))
)

Layer.launch(HttpLive).pipe(NodeRuntime.runMain)

Previously, if a query parameter was defined as a NonEmptyArray (an array that requires at least one element), providing a single value would cause a parsing error.

For example, this worked fine:

curl "http://localhost:3000/?param=1&param=2"

But this would fail:

curl "http://localhost:3000/?param=1"

Resulting in an error because "1" was treated as a string instead of an array.

With this update, single values are automatically wrapped in an array, so they match the expected schema without requiring manual fixes.

[changeset-bot]

🦋 Changeset detected

Latest commit: 04c8d0a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 29 packages

Name	Type
@effect/platform	Patch
@effect/cli	Patch
@effect/cluster-node	Patch
@effect/cluster-workflow	Patch
@effect/cluster	Patch
@effect/experimental	Patch
@effect/platform-browser	Patch
@effect/platform-bun	Patch
@effect/platform-node-shared	Patch
@effect/platform-node	Patch
@effect/rpc-http	Patch
@effect/rpc	Patch
@effect/sql-clickhouse	Patch
@effect/sql-d1	Patch
@effect/sql-libsql	Patch
@effect/sql-mssql	Patch
@effect/sql-mysql2	Patch
@effect/sql-pg	Patch
@effect/sql-sqlite-bun	Patch
@effect/sql-sqlite-node	Patch
@effect/sql	Patch
@effect/ai	Patch
@effect/ai-openai	Patch
@effect/sql-sqlite-do	Patch
@effect/sql-sqlite-react-native	Patch
@effect/sql-sqlite-wasm	Patch
@effect/cluster-browser	Patch
@effect/sql-drizzle	Patch
@effect/sql-kysely	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR