Nixcord. A nicer way to write Vencord config in nix

KaylorBen · July 23, 2024, 2:45am

KaylorBen · July 23, 2024, 2:46am

I wrote this originally just for myself as .toJSON wrapper for Vencord, but I decided to make documentation and stabalize it for others.

I am sure its not perfect, so please leave issues, and comment any concerns.

waffle8946 · July 23, 2024, 4:29am

Regarding your implied question here:

github.com

KaylorBen/nixcord/blob/c023b001af7cb2a7865f10ab335025933ca4cb1c/lib.nix#L29-L34


      
          # this is a really bad solution to this problem, but no matter what all
          # solutions to it are bad, and this is all I can think of after coding
          # for many hours on this
          # technically these are all interchangable in config which is weird
          # so plugins.anonymiseFileNames.method = "cozy" works
          # and is equivilent to plugins.anonymiseFileNames.method = "consistent"

instead of using lib.types.str you can use lib.types.enum to restrict the values that can be provided for an option. It’s mentioned here and the page also has examples of its usage.

Freeform submodules could also help with cleaning up the config/extraConfig duplication, described here.

KaylorBen · July 23, 2024, 4:52am

Thanks! I’ll definitely replace several string fields with enum ones.
This still doesn’t fix the larger issue though which is that all enum values need to map to an arbitrary int value set by the Vencord plugin author. It does help prevent users from inputting different values though which is great.

This will also make documentation more clear if I ever generate docs from source code.

This is now done ^