Erik Lott

What is the status of this issue?

That's tough. Conceptually, it seems to me that as soon as we start dealing with Http requests as Tasks, progress events don't seem to fit well into that story. First,...

> Useful API, but a message cannot be sent to the main application from a task until it completes Definitely. I hope it didn't seem like I was suggesting that....

Whether the final api uses Subs or Cmds, the conceptual outcome is the same: the infrastructure initiates a request, and spews events (progress, ok, err) back to the app in...

In our elm-spa app, we have the required **Pages** folder, along with a **PagesSupport** folder to hold the submodules for individual pages. You have to jump around a bit, but...

> While you could go to great lengths to achieve this - building small packages with interfaces for your domain objects to limit access to internal state - it would...

@hectorgimenez We used to have a lot of internal debate about this very topic, so I feel your pain. In our case, we decided to use unexported fields and fully...

@hectorgimenez, 100%. This pretty much summarizes our experience as well.

Our platform serves photography websites, so SEO friendly urls are an essential feature for us as well. The ideal url structure for us is something like this: `https://www.mydomain.com/image.jpg?w=123&h=234...` I'm experimenting...

I'm experiencing the same issue with the following routes: ``` router = Hanami::Router.new do get "/purchase_orders/:id", to: ->_ {[200, {}, ['show purchase order']]} get "/purchase_orders/:purchase_order_id/items", to: ->_ {[200, {}, ['show...