flake: format

docs/content/tips-n-tricks/k3s/_index.md

@@ -20,6 +20,7 @@ As such, on a server node, we can write kubenix's output there.
   '';
 }
 ```
+
 {{< hint danger >}}
 **WARN**: this will write all manifests to the nix store and is therefore not suitable for inline sensitive data.
 {{< /hint >}}

flake.nix

@@ -15,8 +15,7 @@
 
   outputs = inputs @ {self, ...}:
     (inputs.flake-utils.lib.eachDefaultSystem (
-      system:
-      let
+      system: let
         pkgs = import inputs.nixpkgs {
           inherit system;
           overlays = [self.overlays.default];
@@ -33,12 +32,11 @@
 
         # evalModules with same interface as lib.evalModules and kubenix as
         # special argument
-        evalModules =
-          attrs @ { module ? null
-          , modules ? [ module ]
-          , ...
-          }:
-          let
+        evalModules = attrs @ {
+          module ? null,
+          modules ? [module],
+          ...
+        }: let
           lib' = lib.extend (lib: _self: import ./lib/upstreamables.nix {inherit lib pkgs;});
           attrs' = builtins.removeAttrs attrs ["module"];
         in
@@ -60,8 +58,7 @@
               };
             }
             attrs');
-      in
-      {
+      in {
         inherit evalModules pkgs;
 
         devShells.default = pkgs.mkShell {
@@ -153,15 +150,15 @@
                     #     error: No module found ‹name›/latest
                     # not sure how important that documentation is a this time
                     self.nixosModules.kubenix ["submodule" "submodules"]);
-                }).options;
+                })
+                .options;
             };
           }
           // import ./jobs {
             inherit pkgs;
           };
 
-        checks =
-          let
+        checks = let
           wasSuccess = suite:
             if suite.success
             then pkgs.runCommandNoCC "testing-suite-config-assertions-for-${suite.name}-succeeded" {} "echo success > $out"