lunchcat/sif

chore: handle logging files a different way

vmexec opened this issue · 0 comments

vmexec commented

This still has to be discussed, but logging is really managed badly as of now with each feature spawning its own logger. an optimized way of doing this would be to spawn the loader directly on sif.go, and would then facilitate API output.