Since the new YesodRequest has strict fields, handlerToIO didn't work at all. Even if it did, it had a reference to its parent's ResourceT's internal state, so its chances of blowing up were quite high. The new implementation takes a whitelist approach of taking what we want instead of clearing what we do not want. Also, it takes care of using a new runResourceT. |
||
|---|---|---|
| .. | ||
| Core | ||
| Core.hs | ||