d3adb5/nmonad

A desktop notifications daemon for Linux.

Currently working with DevOps. A few of the things I've worked and / or fiddled with, to some significant extent:

nmonad's Issues

Add tests for NMonad.DBus that spawn temp daemons in containers

To have tests that cover the NMonad.DBus module, it is necessary to make use of DBus daemons, preferably running inside temporary test containers.

Running containers for unit / integration tests is not a new concept, and support for them exists in Haskell to a limited extended in testcontainers. In fact, work into this has been done in test/add-dbus-tests.

DBus authentication and the very package for Haskell have proven to be a bit of a roadblock. Running commands inside provisioned containers, which is straightforward when working with test containers in imperative languages, is also something to look into so we do not depend on packages being installed locally.

Add xmonad-like support for recompilation

XMonad has a self-explanatory recompile command for convenience. It may also attempt to recompile user configuration on start, depending on how it's been set up.

Since one of the goals of this project is to achieve extensibility through behaving as a library more so than an executable, it would be interesting to add support for this to NMonad as well.

Commit to lenses or selectors while eliminating ambiguity

GHC's symbol selection despises ambiguity, and if we start using qualified imports or fully qualified names for record updates or mixing lenses with selectors in the same module, I'm afraid spaghetti code will ensue.

Either we should commit to lenses entirely and dispense selectors through {-# LANGUAGE NoFieldSelectors #-}, or eliminate ambiguity by changing the names of lenses defined in NMonad.Lenses.

Note: the lenses module is being / was added in #4, along with support for basic notification hooks.