Jira issue #
Backport of #
- Bug fix (non-breaking change which fixes an issue)
- New feature/enhancement (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation update
- UI/UX improvement
- Code refactoring (no functional changes)
- Performance improvement
- Tests
- Configuration change
- Infrastructure/build change
- Other (please specify):
Test Steps: 1. 2. 3.
Test Environment:
- Tested locally
- Tested in Storybook
E2E Run:
- Playwright Tests: E2E tests completed successfully (npm run test:e2e)
Unit Tests:
- Unit tests added/updated
- All unit tests pass (npm run test)
- Ran new/updated files in Stryker
Integration Tests:
- Integration tests added/updated
- All integration tests pass
- My code follows the project's style guidelines
- I have performed a self-review of my own code
- I have commented my code, particularly in hard-to-understand areas
- I have removed any console logs and debugging code
- My changes generate no new warnings or errors
- I have checked for and fixed any linting errors (npm run lint)
- Code formatting is correct (npm run prettier:fix)
- I have updated the documentation accordingly
- I have updated the README if necessary
- I have added/updated Storybook stories for new/modified components
- I have updated TypeScript types/interfaces
- My changes follow accessibility best practices
- Interactive elements are keyboard accessible
- Proper ARIA labels and roles are used where needed
- Color contrast meets WCAG standards
- Any dependent changes have been merged and published
- I have updated package dependencies if needed
Does this PR introduce breaking changes?
- Yes
- No