Skip to content

Evaluate if import-tree is a good idea #5

@kylebartz

Description

@kylebartz

I am currently using import tree to import everything in parts/, modules/, and hosts/ to construct the final flake. While this has the nice advantage of not needing to write any import lines, but a distinct disadvantage of not being able to have more control over the imports. For comparison, my current home-ops setup has explicit & declarative imports (kinda) which is verbose but helpful.

An alternative/middle ground to explore is pushing off some configuration to "internal modules" that only get imported by public modules under certain conditions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions