# ui merge

## approach

1. Pull out code that has fewest dependencies as possible (utils, leaf nodes, etc)
2. Tackle rest of code route-by-route
a. start from leaf nodes of route and work up the tree. making sure tests pass at the most granular level
b. if shared code is found while moving over code within routes, move that code over quickly in a separate PR to avoid blocking others
c. ticket tier example: start with presentational component -> container -> overall page and hookup routing

## routes to tackle

Not sure what these routes are for

* `/banned`
* `/inactive`
* `/notallowed`

login routes

* `/createaccount`

App routes

* `/createShipment` - Create shipment page
* `/orders/:orderId/loads/:loadsId` - Loads detail page
* `/orders` - Orders dashboard
* `/dashboard` - Loads dashboard
* `/orders/:orderId` - Single order dashboard
* `/settings` - user settings
* `/shipments` - shipments

## "Error" related components/files
- `utils/errorMapper`

## Misc to keep track of
- `src/utils/consts.ts` constants should be moved inside of file using it

## Components that still need tickets
- CreateAccountForm -- has to be done after form
- components/Dashboard
- DashboardFilter -- has to be done after form
<!-- - DefaultQuery? We should hold off on this // refactor later -->
- NotifcationRow -- has to be done after form and LoadingAnimation
- Notifications
<!-- - LoadDetails----revist next -->
<!-- - QuoteDrawer -->

-components/form

CreateShipment
- CreateShipmentProgress
- CreateShipmentTabs
- CreateShipmentForms