Skip to content

test: add coverage for Tuple.mapFirst, mapSecond, getEquivalence, getOrder#6314

Open
Nicoreia wants to merge 1 commit into
Effect-TS:v3from
Nicoreia:test/tuple-coverage
Open

test: add coverage for Tuple.mapFirst, mapSecond, getEquivalence, getOrder#6314
Nicoreia wants to merge 1 commit into
Effect-TS:v3from
Nicoreia:test/tuple-coverage

Conversation

@Nicoreia

Copy link
Copy Markdown

What

Adds unit tests for four previously-untested Tuple exports:

  • Tuple.mapFirst
  • Tuple.mapSecond
  • Tuple.getEquivalence
  • Tuple.getOrder

Why

These functions are part of the public Tuple API but had no test coverage. The
new tests exercise both the data-first and the pipeable (data-last) call forms
for mapFirst/mapSecond, and the equality / ordering semantics of
getEquivalence and getOrder (equal, less-than, greater-than cases).

Scope

Test-only — no source or behavior changes, so no changeset is included (this PR
does not cause a version bump).

Validation

  • vitest for the Tuple suite passes locally.
  • The asserted outputs were independently re-verified against the published
    effect runtime before submission.

Disclosure

This contribution was prepared with AI assistance (Claude) and reviewed and
verified by the author before submission.

The exported functions `mapFirst`, `mapSecond`, `getEquivalence` and
`getOrder` had no unit tests. Add cases following the existing Tuple test
style: both data-first and data-last forms for `mapFirst`/`mapSecond`, and
equal/less/greater checks for `getEquivalence` and `getOrder`.
@changeset-bot

changeset-bot Bot commented Jul 10, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 9003cd9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@IMax153 IMax153 changed the base branch from main to v3 July 13, 2026 23:55
@IMax153 IMax153 added the 3.0 Used for issues, pull requests, etc. that are relevant for the `v3` branch targeting Effect v3. label Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0 Used for issues, pull requests, etc. that are relevant for the `v3` branch targeting Effect v3.

Projects

Status: Discussion Ongoing

Development

Successfully merging this pull request may close these issues.

2 participants