Skip to content

Latest commit

 

History

History
75 lines (62 loc) · 2.37 KB

File metadata and controls

75 lines (62 loc) · 2.37 KB

Summary

Brief description of what this PR does and why it's needed.

Type of Change

  • 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)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Test addition/update

Changes Made

Related Issues

Closes # Fixes # Relates to #

Testing

  • Unit tests added/updated
  • All existing tests pass
  • Manual testing performed
  • Integration tests added (if applicable)

Test Coverage

  • New code has >90% test coverage
  • Edge cases are covered
  • Error scenarios are tested

Pre-submission Checklist

  • All commits follow conventional format (type(scope): description)
  • Each commit is atomic (one logical change per commit)
  • All tests pass: npm test
  • Code is properly formatted: npm run format
  • No linting errors: npm run lint
  • TypeScript compiles: npm run typecheck
  • Build succeeds: npm run build
  • Branch is up to date with main branch
  • Self-reviewed the changes before requesting review

Documentation

  • JSDoc comments added for new public APIs
  • README updated (if needed)
  • Breaking changes documented
  • Migration guide provided (for breaking changes)

Performance Impact

  • No performance impact
  • Performance improvement (describe)
  • Potential performance regression (describe and justify)

Backwards Compatibility

  • Fully backwards compatible
  • Deprecates existing functionality (provide timeline)
  • Breaking change (increment major version)

Screenshots/Examples

Additional Notes


Reviewer Note: Please ensure this PR follows our Contributing Guidelines and meets all code review criteria.