Skip to content

fix(string): 🐛 constrain titleCase property test to non-whitespace words#55

Merged
baxyz merged 1 commit intomainfrom
still-for-alpha-20
Apr 25, 2026
Merged

fix(string): 🐛 constrain titleCase property test to non-whitespace words#55
baxyz merged 1 commit intomainfrom
still-for-alpha-20

Conversation

@baxyz
Copy link
Copy Markdown
Contributor

@baxyz baxyz commented Apr 25, 2026

Description

Please include a summary of what this PR does and why it's needed.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring
  • Test improvement

Related Issues

Closes #(issue number)

How Has This Been Tested?

Describe the tests you ran and how to reproduce them:

  • Test A
  • Test B

Checklist

  • My code follows the code style of this project
  • I have updated the documentation accordingly
  • I have added tests for my changes
  • All new and existing tests passed locally
  • My commits follow the conventional commit format

Screenshots (if applicable)

Add screenshots for UI changes.

Additional Context

Add any other context about the PR here.

Copilot AI review requested due to automatic review settings April 25, 2026 18:51
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adjusts the titleCase property-based test generator to avoid invalid “word” inputs that can lead to misleading failures, improving test reliability for multi-word behavior.

Changes:

  • Constrains generated words in the multi-word property test to exclude whitespace-only strings.
  • Refactors the property declaration formatting for readability.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread helpers/string/titleCase.spec.ts Outdated
@baxyz baxyz force-pushed the still-for-alpha-20 branch from 964dd0c to caf9c0f Compare April 25, 2026 18:57
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 25, 2026

✅ PR Validation Passed

All checks passed and coverage target reached!


📋 Pipeline Status

Job Status
🔢 Version passing
🏗️ Build passing
🧪 Tests passing
📝 Lint passing
📘 TypeCheck passing
🔐 Security Audit passing
🧾 Conventional Commits passing
🔗 Coherency passing

📊 Code Coverage

Overall Coverage: 100.0% — Target reached! 🎯

Metric Progress Coverage
Lines ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100%
Branches ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100%
Functions ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100%
Statements ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100%

🧬 Mutation Testing

🟢 Mutation Score: 92.39% — excellent

Metric Progress Score
🟢 Mutation Score ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░ 92.39%

🧬 Mutation testing is informational only and does not block the PR

📊 View full mutation report on Stryker Dashboard


🌐 Runtime Compatibility

Runtime Compatibility: 3/3 — All runtimes passed!

Runtime Status
🟩 Node.js 24 (LTS) v24.14.1
🦕 Deno 2.7.13
🍞 Bun 1.3.13

🔄 Runtime compatibility is informational only and does not block the PR


⏱️ Benchmarks

Benchmarks: 0 suites — completed

⏱️ Benchmarks are informational only and do not block the PR


ℹ️ About this report
  • 🎯 Coverage Target: 100% for all metrics
  • 🧬 Mutation Testing: powered by Stryker (non-blocking)
  • ⏱️ Benchmarks: powered by Vitest Bench (non-blocking)
  • 🔄 This comment updates automatically with each push
  • 📈 Coverage is measured using Vitest + v8

🤖 Generated by @helpers4 CI • 2026-04-25

@baxyz baxyz force-pushed the still-for-alpha-20 branch from caf9c0f to d4fce16 Compare April 25, 2026 19:12
@baxyz baxyz merged commit 20dbc56 into main Apr 25, 2026
15 checks passed
@baxyz baxyz deleted the still-for-alpha-20 branch April 25, 2026 19:44
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