-
Jamie Tanna authored
Although we still want to use charmbracelet/log under the hood, this allows us to use a more consistent interface, and doesn't require each usage of the logger to know what the underlying handler is. This requires we pin to my fork until upstream have released the changes. Closes #160.
95039637Jamie Tanna authoredAlthough we still want to use charmbracelet/log under the hood, this allows us to use a more consistent interface, and doesn't require each usage of the logger to know what the underlying handler is. This requires we pin to my fork until upstream have released the changes. Closes #160.
Loading