03:46:19  * MEGAGHZjoined
04:59:16  * MEGAGHZquit (Quit: Control C)
08:51:07  * dobsonquit (Ping timeout: 260 seconds)
09:53:45  * dobsonjoined
10:20:38  * dobsonquit (Read error: Connection reset by peer)
10:31:22  * dobsonjoined
13:34:04  * muh-die-kuhquit (Quit: No Ping reply in 180 seconds.)
13:35:13  * muh-die-kuhjoined
13:43:49  * muh-die-kuhquit (Quit: No Ping reply in 210 seconds.)
13:58:00  * muh-die-kuhjoined
15:32:46  * markinquit (Ping timeout: 248 seconds)
15:34:34  * markinjoined
16:15:46  * muh-die-kuhquit (Quit: No Ping reply in 180 seconds.)
16:17:09  * muh-die-kuhjoined
17:09:56  * MrFahrenheitjoined
17:12:09  <MrFahrenheit>is it possible without too much effort to have routes that go like this: "customers/4" - gets customer with id 4, "customers/4/items" - gets items for customer with id 4, and then also "customers/items" which gets all items for all customers
17:12:27  <MrFahrenheit>and using nested routers
17:14:50  <MrFahrenheit>never mind, it seems just making a route like "customers/:customerId?/items" works
17:40:13  * muh-die-kuhquit (Quit: No Ping reply in 180 seconds.)
17:56:46  * muh-die-kuhjoined
21:34:49  * muh-die-kuhquit (Ping timeout: 240 seconds)
21:35:51  * muh-die-kuhjoined
23:55:02  * Evanionjoined