in ManageTrainScheduleV2, some major transformation on pathfinding data is delegated to sub components TypeAndPathV2.
launchPathFinding has much more responsibility than a mere (and small) subcomponent should have
I think that’s a design flaw and a case where props drilling is problematic. it creates major indirection: difficult to follow where to data comes from and what’s done to it.
This really could be a proper case to use a business hook (as proposed by @jacomyal @sim51)
to be discussed
Description and goal
in
ManageTrainScheduleV2
, some major transformation on pathfinding data is delegated to sub componentsTypeAndPathV2
.launchPathFinding has much more responsibility than a mere (and small) subcomponent should have
I think that’s a design flaw and a case where props drilling is problematic. it creates major indirection: difficult to follow where to data comes from and what’s done to it.
This really could be a proper case to use a business hook (as proposed by @jacomyal @sim51) to be discussed