NA

Description

Fixes #(issue number)

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
• Performance improvement
• Code refactoring
• Test coverage improvement

Changes Made

Testing

• All existing tests pass (devtools::test())
• Added new tests for new functionality
• Tested manually with real Strava data
• R CMD check passes with no errors, warnings, or notes
• Code coverage maintained or improved

Test results

# Paste relevant test output here

Documentation

• Updated function documentation (roxygen2)
• Updated README (if applicable)
• Updated NEWS.md
• Updated vignettes (if applicable)
• All examples run successfully

Code Quality

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have checked for and resolved any merge conflicts

Dependencies

• No new dependencies added
• New dependencies added (list below with justification)
  • Package:
  • Reason:

Breaking Changes

Does this PR introduce breaking changes? - [ ] Yes - [ ] No

If yes, please describe: - What breaks: - How to migrate:

Additional Notes

Checklist for Reviewers

• Code follows project conventions
• Tests are adequate and pass
• Documentation is complete and accurate
• Changes are backwards compatible (or breaking changes are justified and documented)
• NAMESPACE and DESCRIPTION are updated if needed
• NEWS.md is updated

---

Note: By submitting this pull request, I confirm that my contribution is made under the terms of the MIT License and I have read and agree to the Code of Conduct.