Refactor date range formatting using enum-based approach.

[Adebesin-Cell]

Refactor date range formatting using enum-based approach for improved maintainability

Description

This PR introduces a significant refactoring of the date range formatting functionality. The main goal is to improve code organization, readability, and maintainability while preserving the existing behavior. The changes introduce an enum-based approach to categorize different date range scenarios, allowing for a more structured and extensible codebase.

Changes Made

1. Introduced DateRangeType enum to categorize different date range scenarios.
2. Refactored formatDateRange function to use a switch statement based on DateRangeType.
3. Extracted individual formatting functions for each date range type:
   • formatYear
   • formatQuarter
   • formatMonth
   • formatAcrossYears
   • formatAcrossMonths
   • formatAcrossDays
   • formatSameDay
4. Improved code organization by grouping related functions together.
5. Enhanced type safety with the use of enums and more specific function signatures.
6. Maintained existing functionality and output format.

Motivation

The previous implementation of date range formatting, while functional, lacked clear separation of concerns for different date range scenarios. This refactoring aims to make the code more modular, easier to understand, and simpler to extend in the future.

Testing

• Existing unit tests have been updated to accommodate the new structure.
• Manual testing has been performed to ensure output consistency with the previous implementation.

Performance Considerations

While the new implementation introduces additional function calls, the performance impact is expected to be negligible. The benefits in code clarity and maintainability outweigh any minor performance costs.

Additional Notes for Reviewers

• Pay special attention to the determineDateRangeType function, as it's crucial for correctly categorizing date ranges.
• The formatSameDay function now takes an object as an argument for improved readability. Please review if this approach aligns with the project's conventions.
• Consider if any edge cases might have been overlooked in this refactoring.

---

Thank you for reviewing this PR. Your feedback and suggestions are greatly appreciated!