refactor(booking-single-view): Refactor RecurringBookings and add hoo… #15400
+454
−5,575
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactor Overview
The primary goal was to reduce the complexity of the RecurringBookings component as identified by Codescene. The refactors included breaking down the component into smaller, more manageable pieces, and moving specific logic into utility functions and subcomponents.
Changes Made
Subcomponents: Introduced a subcomponent RecurringEvent to handle individual event rendering.
Component Refactor: Updated the RecurringBookings component to utilize the new utility functions and subcomponent, improving readability and maintainability.
Codescene Analysis
Codescene identified the RecurringBookings component as a complex method due to numerous conditional statements and nested logic. The refactor addresses these issues by modularizing the code.