Yang, Bo

If we want to get those features done on the type-level, those functions should be created as separated type classes

``` scala trait MyPlugin { type T @inject(isTransient = true, isLazy = true) val xxx: T

According to https://docs.github.com/en/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github , `.gitattributes` file can be used to tell GitHub a file is generated and the changes to the files will be hidden by default in pull requests....

docs: recommend setting `moduleLocation` by default

4

As `moduleLocation` can be used to avoid portential infinite loops issue, it would be nice to mention it from README.

Set `_file` and `_class` for modules defined under `flake.modules.${className}.${moduleName}`

1

In https://github.com/NixOS/nixpkgs/pull/197547 > I do not expect users or module authors to set the class attribute in their modules (although they may). Instead I envision a library like [flake-parts](https://flake.parts/) to...

This PR is a rework of https://github.com/hercules-ci/flake-parts/pull/156. It avoids infinite loops by using partitions.

Cannot access `inputs.self.outPath` in top level `imports`

4

## Given ``` nix # flake.nix { inputs.flake-parts.url = "github:hercules-ci/flake-parts"; outputs = inputs@{ self, flake-parts, ... }: flake-parts.lib.mkFlake { inherit inputs; } ({inputs, ...}: { imports = [ "${inputs.self.outPath}/my-module.nix" ];...