From Discord: Potential Bug in Match.tags with Undefined Input

[effect-bot]

Summary

The discussion is about a potential bug in the Match.tags feature of the Effect TypeScript library when handling undefined inputs. The user _adrian_g expects the Match.tags function to properly handle an undefined input by falling back to the orElse case and returning null, as it does in the Match.when case. Instead, it throws a TypeError because it tries to read a property of undefined.

Another user, patroza, suggests that Match.tags should adopt the same semantics as Match.when, where non-object inputs are skipped to avoid such errors. patroza also provides an example showing that the code works with defined types other than undefined.

Key takeaways:

1. There is an inconsistency in how Match.when and Match.tags handle undefined inputs.
2. The issue causes a runtime error when using Match.tags with an undefined value.
3. It is suggested that Match.tags be modified to handle these cases similarly to Match.when.
4. _adrian_g is inquiring about the process for creating a GitHub issue to report the bug. patroza hints at using a command to initiate issue creation.

Discord thread

https://discord.com/channels/795981131316985866/1330857990076628992