Currently, the file name argument is passed through lumberjack.WithFileName() option when initializing the writer. It would be convenient (well, for me at least as a DI and isolation fan) to pass some kind of file system interface for integration and acceptance testing scenarios, where the mock file system is being used. The similar interface is defined in this package: https://github.com/hack-pad/hackpadfs.
If you want me to create a MR, let me know in the comments for this issue.
Currently, the file name argument is passed through
lumberjack.WithFileName()option when initializing the writer. It would be convenient (well, for me at least as a DI and isolation fan) to pass some kind of file system interface for integration and acceptance testing scenarios, where the mock file system is being used. The similar interface is defined in this package: https://github.com/hack-pad/hackpadfs.If you want me to create a MR, let me know in the comments for this issue.