v2.0.0-rc2

This release changes the v2/flumetest package. It removes the XXXSetDefault() functions and support for configuring log settings from a special, test-specific environment variable (the "config string").

These features presumed that the flumetest package should be used both in your TestMain() as well as at the beginning of each test. But this was too opinionated. The stuff it flumetest was doing in Start() (in test cases) was not related or dependent on the stuff it was doing in SetDefaults() (which was mainly concerned with offering sensible default log settings for tests).

It is simpler and less opinionated for consumers to just use the same flume.ConfigFromEnv() function in TestMain() as they use in Main(). If they want to use different defaults, they can do so trivially in their own code, or write their own setup function for tests. Trying to standardize this in flumetest created complicated problems with ordering of configuration and bootstrap stuff.

• BREAKING CHANGE Removed SetDefault(), MustSetDefault, and "-log-config" support are removed
• Improved inline docs

v2.0.0-rc2

What's Changed

• Fixes #2 by @ansel1 in #3
• Minor doc clarification

Full Changelog: v1.0.0...v2.0.0-rc2

Release v2.0.0-rc

This is the release candidate for version 2.0.0.

Release v1.0.0

Promoting the original flume to 1.0.0, which is now deemed stable.
Backward compatibility will be guaranteed in future 1.x.x releases.
It is not expected that v1.x.x development will add any major new features, just bug fixes.

Release v2 alpha

Alpha release of flume v2.

The big change is that v2 works with slog instead of zap. It creates slog.Handlers, which can be dynamically reconfigured to different levels, and different backend Handlers.

Release 0.13.1

Just dependency updates.

Release 0.13.0

Added hooks. HookFuncs can be added at the factory level or the logger level, and are called right before an entry is logged. They can modify the fields included in the logged entry. See Hooks() and AddHooks().

Release 0.12.0

Added IsInfo() bool to Logger interface. There are occasions where info logging code might still be performance sensitive, and should be disabled.

0.11.3

flumetest.Start() was not concurrency safe: the buffer it used to accumulate logs while the test was running was not safe for concurrent use. Now uses a buffer protected by a mutex.

Release 0.11.2

• Configure(): Fixed a bug where the DefaultLevel setting was being ignored
• when passing a single, bare value as the args to logger functions, flume will add a key/value pair to the log entry, using an empty string as the key. This has been tweaked: if the value is an error, then the key will be "error"