Skip to content

Conversation

@interim17
Copy link
Contributor

Time Estimate or Size

How long do you expect it to take a reviewer to review this PR?
Alternately, is this PR xsmall, small, medium, large, or xlarge?

Problem

What is the problem this work solves, including
Link to story or ticket

Solution

What I/we did to solve this problem

with @pairperson1

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • This change requires updated or new tests

Change summary:

  • Tidy, well formulated commit message
  • Another great commit message
  • Something else I/we did

Steps to Verify:

  1. A setup step / beginning state
  2. What to do next
  3. Any other instructions
  4. Expected behavior
  5. Suggestions for testing

Screenshots (optional):

Show-n-tell images/animations here

Keyfiles (delete if not relevant):

  1. main file/entry point
  2. other important file

Thanks for contributing!

@github-actions
Copy link

github-actions bot commented Jul 24, 2025

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 23.07% 2583 / 11195
🔵 Statements 23.07% 2583 / 11195
🔵 Functions 25% 149 / 596
🔵 Branches 80.41% 349 / 434
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
src/index.ts 100% 100% 100% 100%
Generated in workflow #615 for commit df0c8df by the Vitest Coverage Report Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants