fix: Match.tags throwing on undefined input

[giuliobracci]

Type

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

By testing out 4303 I could successfully reproduce the issue.

I followed the stack trace and verified that there was no check for null or undefined before executing the unsafe type introspection with the key in object syntax.

Related

• Related Issue From Discord: Potential Bug in Match.tags with Undefined Input #4303
• Closes From Discord: Potential Bug in Match.tags with Undefined Input #4303

[changeset-bot]

🦋 Changeset detected

Latest commit: 4f28fe6

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

This PR includes changesets to release 36 packages

Name	Type
effect	Patch
@effect/cli	Patch
@effect/cluster-browser	Patch
@effect/cluster-node	Patch
@effect/cluster-workflow	Patch
@effect/cluster	Patch
@effect/experimental	Patch
@effect/opentelemetry	Patch
@effect/platform-browser	Patch
@effect/platform-bun	Patch
@effect/platform-node-shared	Patch
@effect/platform-node	Patch
@effect/platform	Patch
@effect/printer-ansi	Patch
@effect/printer	Patch
@effect/rpc-http	Patch
@effect/rpc	Patch
@effect/sql-clickhouse	Patch
@effect/sql-d1	Patch
@effect/sql-drizzle	Patch
@effect/sql-kysely	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-do	Patch
@effect/sql-sqlite-node	Patch
@effect/sql-sqlite-react-native	Patch
@effect/sql-sqlite-wasm	Patch
@effect/sql	Patch
@effect/typeclass	Patch
@effect/vitest	Patch
@effect/ai	Patch
@effect/ai-anthropic	Patch
@effect/ai-openai	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