e59b0a1c88
They work fine. But I had to go to a lot of trouble to get Yesod to render routes in a pure function. It may instead make more sense to have each alert have an assocated IO action, and a single route that runs the IO action of a given alert id. I just wish I'd realized that before the past several hours of struggling with something Yesod really doesn't want to allow. |
||
---|---|---|
.. | ||
Pairing | ||
Threads | ||
WebApp | ||
Alert.hs | ||
Changes.hs | ||
Commits.hs | ||
Common.hs | ||
DaemonStatus.hs | ||
Pairing.hs | ||
Pushes.hs | ||
ScanRemotes.hs | ||
Sync.hs | ||
ThreadedMonad.hs | ||
TransferQueue.hs | ||
TransferSlots.hs | ||
WebApp.hs |