Project

General

Profile

Actions
Copy link

Improvement #31888

open

Improvement #31248: New Theme based Nextjs application dev analysis

Improvement #31630: Implement flight result page

flight result page views architeture

Added by Sachin Suresh 3 months ago. Updated 3 months ago.

Status:
Fixed not Tested
Priority:
Normal
Assignee:
Sachin Suresh
Target version:
-
Start date:
01/01/2026
Due date:
01/01/2026 (about 3 months late)
% Done:

100%

Estimated time:
Spent time:
8:00 h
remarks:
DB Changes:
Keys & Permissions:
Areas Affected:
Files Changed:
Actions
Copy link
 #1

Updated by Sachin Suresh 3 months ago

  • Status changed from Assigned to In Progress
Actions
Copy link
 #2

Updated by Sachin Suresh 3 months ago

  • Status changed from In Progress to Fixed not Tested
  • % Done changed from 0 to 100

Expanded Results Components (Refactor)
The following components were added to modularize the "View Fares" and "Details" sections, strictly following the Core/View architecture:

Branded Fares
Core:

BrandedFaresCore
(Logic placeholder)
View:

BrandedFaresView
(Displays "Select Fare Type" carousel/list)
Flight Details
Core:

FlightDetailsCore
(Manages active tab handling)
View:

FlightDetailsView
(Tabbed container)
Sub-Views:

FlightSegmentDetailsView
: Flight legs, baggage, layovers.

FareSummaryView
: Price breakdown table.

FareRulesView
: Cancellation and change fees.
Architecture Refinement
View Composition: Refactored

FlightResultItemView
to instantiate

BrandedFaresCore
and

FlightDetailsCore
directly within the JSX, rather than accepting them as props. This aligns with the project's pattern where Views compose their sub-features (Core/View pairs).
These components are integrated into

FlightResultItemView
via props passed from

FlightResultItemCore
, ensuring the View remains pure.

Actions
Copy link

Also available in: Atom PDF