fricklerhandwerk
pushed to data-model-as-diagram at fricklerhandwerk/Fediversity
2025-07-02 03:39:40 +02:00
fricklerhandwerk
pushed to data-model-as-diagram at fricklerhandwerk/Fediversity
2025-07-02 01:20:42 +02:00
fricklerhandwerk
pushed to data-model-as-diagram at fricklerhandwerk/Fediversity
2025-07-01 22:07:46 +02:00
Inject sources, secrets and keys via module system - avoid `import ../`
fricklerhandwerk
pushed to data-model-as-diagram at fricklerhandwerk/Fediversity
2025-07-01 17:55:53 +02:00
fricklerhandwerk
pushed to data-model-as-diagram at fricklerhandwerk/Fediversity
2025-07-01 17:54:10 +02:00
fricklerhandwerk
created branch data-model-as-diagram in fricklerhandwerk/Fediversity
2025-07-01 17:52:45 +02:00
fricklerhandwerk
pushed to data-model-as-diagram at fricklerhandwerk/Fediversity
2025-07-01 17:52:45 +02:00
Compare 10 commits »
Inject sources, secrets and keys via module system - avoid
import ../
Why not pass the location of secrets via some module option instead? But to be clear, this is already overall a lot better than it was before.
WIP: Use
closureInfo
to avoid having to declare extra dependencies manually
We likely won't incur an extra development cost in figuring out dependencies any time soon. We can revisit that topic when we do; first let's spiral up the domain model until we run into the…
Inject sources, secrets and keys via module system - avoid
import ../
but why are these per-system? it's just files, no?
alleviate pain from tests requiring to manually specify
extraDependencies
Inject sources, secrets and keys via module system - avoid
import ../
It's an alright tech debt reduction, let's do small steps in the agreed-upon direction.
move shell from flake