Log layer design

[h2non]

My idea is to build a minimalistic logging layer build on top of logrus, having the ability to use a default logger (used by core vinxi package) or alternatively use custom loggers.

In order to make it very simple to use, I think the package should expose a singleton style logger interface, such as (log package consumer side):

import "gopkg.in/vinxi/log.v0"

func main() {
  log.Printf("Write something: %s", "foo")
  log.Debug("Debug message")
  ...
}

From the other side, developers should be able to build and reuse custom loggers with custom formatters and listeners. Possible example:

import "gopkg.in/vinxi/log.v0"

var logConfig := log.NewConfig(...)
var myLog := log.New("myLog", logConfig) // implicitly registered

func main() {
  myLog.Printf("Write something: %s", "foo")
  myLog.Debug("Debug message")
  ...
  // Or you can also retrieve the previously created logger
  log.Logger("myLog").Warm("Got it")
}

[h2non]

@groyoh What do you think?

[groyoh]

var myLog := log.New("myLog", logConfig)

Would you have to do that for every file or just once the main file?
Also, can you only pass the config for the logger or can you pass a custom logger itself?

[h2non]

If using the generic built-in logger, you won't have to do never, just import tha package.

If using a custom logger, only have to do once time.

[h2non]

Generic logging layer is done. We could consider implementing a logger global store as I described above in order to easily register and fetch logger instances from other packages without the instantiation boilerplate.

My opinion is that we could support that in the future when we actually need it more. Should be trivial to support anyway.