Jordan
The reason I wrote mine separately as I see my project being primarily a module for home-manager. My vision for homeage doesn't involve a CLI (interested only in the module)...
Testing plan: 1. Start with signed cookies due to #16 (something that should be caught by testing)
Thanks for the contribution sorry for the slow response. I will try and get around to looking it over this week.
The frontend contains the methods that interact with the requests/responses. For example the signed cookie signs the session id and then creates a cookie and attaches it to the response....
That's a good idea. 1. A list of source files (in activation/service folders) which are removed unprompted. 2. A list of copied files which are removed by prompt. 3. Symlinks...
Ah, didn't realize the NixOS module thing. I'll make it an option that defaults to `keep`. Plan is to use `rm -i` to prompt for deleting the file. This is...
Thanks for the PR but I am gonna let it set for a bit as I need to get the activation checks and cleanup stable before adding anymore features right...
> Just a sidenote because I forgot again: `options.md` should be auto-generated, otherwise it will always be somehow outdated.. (Not sure why you created that file in the first place...
Added notes on current state of cleanup to README
Due to issues with installing certain tree sitter plugins with Nix, I've commented out the tree sitter install *for now* and just manually download them with `:TSInstall`.