[Provide a clear and concise description of the changes introduced by this PR. Explain what was changed and why it was changed. Link to any related issues or tasks using keywords like Closes #123 or Fixes #456.]
- 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)
- Refactor (code improvement or restructuring without changing external behavior)
- Documentation update
- Chore (e.g., dependency updates, build tooling changes)
[Describe the testing you have performed to ensure the changes work as expected. Include details about:
- Unit tests
- Integration tests
- Manual testing steps (if applicable, provide specific instructions for reviewers to verify the changes)
- Screenshots or GIFs (if relevant, especially for UI changes)]
- My code follows the project's coding 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 made corresponding changes to the documentation (if necessary).
- My changes generate no new warnings.
- I have added tests that prove my fix is effective or my feature works.
- New and existing unit tests pass locally with my changes.
[Add any other relevant information for the reviewers, such as potential performance impacts, known limitations, or alternative solutions considered during development.]