sidebarDepth | search |
---|---|
0 |
false |
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
1.19.2 - 2023-02-21
- Upgrade Dig dependency to v1.16.1.
1.19.1 - 2023-01-10
- Calling
fx.Stop()
after theApp
has already stopped no longer errors out.
- Addressed a regression in 1.19.0 release which caused apps to ignore OS signals after running for startTimeout duration.
1.19.0 - 2023-01-03
fx.RecoverFromPanics
Option which allows Fx to recover from user-provided constructors and invoked functions.fx.Private
that allows the constructor to limit the scope of its outputs to the wrappingfx.Module
.ExitCode
ShutdownOption which allows setting custom exit code at the end of app lifecycle.Wait
which returns a channel that can be used for waiting on application shutdown.- fxevent/ZapLogger now exposes
UseLogLevel
andUseErrorLevel
methods to set the level of the Zap logs produced by it. - Add lifecycle hook-convertible methods:
StartHook
,StopHook
,StartStopHook
that can be used with more function signatures.
fx.WithLogger
can now be passed atfx.Module
level, setting custom logger atModule
scope instead of the wholeApp
.
fx.OnStart
andfx.OnStop
Annotations now work with annotated types that was provided by the annotated constructor.- fxevent/ZapLogger: Errors from
fx.Supply
are now logged atError
level, notInfo
. - A race condition in lifecycle Start/Stop methods.
- Typos in docs.
1.18.2 - 2022-09-28
- Clarify ordering of
Invoke
s inModule
s.
- Fix
Decorate
not being applied to transitive dependencies at rootApp
level.
1.18.1 - 2022-08-08
- Fix a nil panic when
nil
is passed toOnStart
andOnStop
lifecycle methods.
1.18.0 - 2022-08-05
- Soft value groups that lets you specify value groups as best-effort dependencies.
fx.OnStart
andfx.OnStop
annotations which lets you annotate dependencies to provide OnStart and OnStop lifecycle hooks.- A new
fxevent.Replaced
event written tofxevent.Logger
following anfx.Replace
.
- Upgrade Dig dependency to v1.14.1 to address a couple of issues with decorations. Refer to Dig v1.14.1 release notes for more details.
fx.WithLogger
no longer ignores decorations and replacements of types that it depends on.- Don't run lifecycle hooks if the context for them has already expired.
App.Start
andApp.Stop
no longer deadlock if the OnStart/OnStop hook exits the current goroutine.fxevent.ConsoleLogger
no longer emits an extraneous argument for the Supplied event.
fx.Extract
in favor offx.Populate
.
1.17.1 - 2022-03-23
- Logging for provide/invoke/decorate now includes the associated
fx.Module
name.
1.17.0 - 2022-02-28
- Add
fx.Module
which scopes any modifications made to the dependency graph. - Add
fx.Decorate
andfx.Replace
that lets you modify a dependency graph with decorators. - Add
fxevent.Decorated
event which gets emitted upon a dependency getting decorated.
fx.Annotate
: Validate thatfx.In
orfx.Out
structs are not passed to it.fx.Annotate
: Upon failure to Provide, the error contains the actual location of the provided constructor.
1.16.0 - 2021-12-02
- Add the ability to provide a function as multiple interfaces at once using
fx.As
.
fx.Annotate
: support variadic functions, and feeding value groups into them.
- Fix an issue where OnStop hooks weren't getting called on SIGINT on Windows.
- Fix a data race between app.Done() and shutdown.
1.15.0 - 2021-11-08
- Add
fx.Annotate
to allow users to provide parameter and result tags easily without having to createfx.In
orfx.Out
structs. - Add
fx.As
that allows users to annotate a constructor to provide its result type(s) as interface(s) that they implement instead of the types themselves.
- Fix
fxevent.Stopped
not being logged whenApp.Stop
is called. - Fix
fxevent.Started
orfxevent.Stopped
not being logged when start or stop times out.
1.14.2 - 2021-08-16
- For
fxevent
console implementation: no longer log non-error case forfxevent.Invoke
event, while for zap implementation, start loggingfx.Invoking
case without stack.
1.14.1 - 2021-08-16
fxevent.Invoked
was being logged atError
level even upon successfulInvoke
. This was changed to log atInfo
level whenInvoke
succeeded.
1.14.0 - 2021-08-12
- Introduce the new
fx.WithLogger
option. Provide a constructor forfxevent.Logger
objects with it to customize how Fx logs events. - Add new
fxevent
package that exposes events from Fx in a structured way. Use this to write custom logger implementations for use with thefx.WithLogger
option. - Expose and log additional information when lifecycle hooks time out.
- Fx now emits structured JSON logs by default. These may be parsed and processed by log ingestion systems.
fxtest.Lifecycle
now logs to the providedtesting.TB
instead of stderr.fx.In
andfx.Out
are now type aliases instead of structs.
1.13.1 - 2020-08-19
- Fix minimum version constraint for dig.
fx.ValidateGraph
requires at least dig 1.10.
1.13.0 - 2020-06-16
- Added
fx.ValidateGraph
which allows graph cycle validation and dependency correctness without running anything. This is useful iffx.Invoke
has side effects, does I/O, etc.
1.12.0 - 2020-04-09
- Added
fx.Supply
to provide externally created values to Fx containers without building anonymous constructors.
- Drop library dependency on development tools.
1.11.0 - 2020-04-01
- Value groups can use the
flatten
option to indicate values in a slice should be provided individually rather than providing the slice itself. See package documentation for details.
1.10.0 - 2019-11-20
- All
fx.Option
s now include readable string representations. - Report stack traces when
fx.Provide
andfx.Invoke
calls fail. This should make these errors more debuggable.
- Migrated to Go modules.
1.9.0 - 2019-01-22
- Add the ability to shutdown Fx applications from inside the container. See the Shutdowner documentation for details.
- Add
fx.Annotated
to allow users to provide named values without creating a new constructor.
1.8.0 - 2018-11-06
- Provide DOT graph of dependencies in the container.
1.7.1 - 2018-09-26
- Make
fxtest.New
ensure that the app was created successfully. Previously, it would return the app (similar tofx.New
, which expects the user to verify the error). - Update dig container to defer acyclic validation until after Invoke. Application startup time should improve proportional to the size of the dependency graph.
- Fix a goroutine leak in
fxtest.Lifecycle
.
1.7.0 - 2018-08-16
- Add
fx.ErrorHook
option to allow users to provideErrorHandler
s on invoke failures. VisualizeError
returns the visualization wrapped in the error if available.
1.6.0 - 2018-06-12
- Add
fx.Error
option to short-circuit application startup.
1.5.0 - 2018-04-11
- Add
fx.StartTimeout
andfx.StopTimeout
to make configuring application start and stop timeouts easier. - Export the default start and stop timeout as
fx.DefaultTimeout
.
- Make
fxtest
respect the application's start and stop timeouts.
1.4.0 - 2017-12-07
- Add
fx.Populate
to populate variables with values from the dependency injection container without requiring intermediate structs.
1.3.0 - 2017-11-28
- Improve readability of hook logging in addition to provide and invoke.
- Fix bug which caused the OnStop for a lifecycle hook to be called even if it failed to start.
1.2.0 - 2017-09-06
- Add
fx.NopLogger
which disables the Fx application's log output.
1.1.0 - 2017-08-22
- Improve readability of start up logging.
1.0.0 - 2017-07-31
First stable release: no breaking changes will be made in the 1.x series.
fx.Extract
now supportsfx.In
tags on target structs.
- [Breaking] Rename
fx.Inject
tofx.Extract
. - [Breaking] Rename
fxtest.Must*
tofxtest.Require*
.
- [Breaking] Remove
fx.Timeout
andfx.DefaultTimeout
.
1.0.0-rc2 - 2017-07-21
- [Breaking] Lifecycle hooks now take a context.
- Add
fx.In
andfx.Out
which exposes optional and named types. Modules should embed these types instead of relying ondig.In
anddig.Out
. - Add an
Err
method to retrieve the underlying errors during the dependency graph construction. The same error is also returned fromStart
. - Graph resolution now happens as part of
fx.New
, rather than at the beginning ofapp.Start
. This allows inspection of the graph errors throughapp.Err()
before the decision to start the app. - Add a
Logger
option, which allows users to send Fx's logs to different sink. - Add
fxtest.App
, which redirects log output to the user'stesting.TB
and provides some lifecycle helpers.
1.0.0-rc1 - 2017-06-20
- [Breaking] Providing types into
fx.App
and invoking functions are now options passed during application construction. This makes users' interactions with modules and collections of modules identical. - [Breaking]
TestLifecycle
is now in a separatefxtest
subpackage. - Add
fx.Inject()
to pull values from the container into a struct.
1.0.0-beta4 - 2017-06-12
- [Breaking] Monolithic framework, as released in initial betas, has been
broken into smaller pieces as a result of recent advances in
dig
library. This is a radical departure from the previous direction, but it needed to be done for the long-term good of the project. - [Breaking]
Module interface
has been scoped all the way down to being a single dig constructor. This allows for very sophisticated module compositions. Seego.uber.org/dig
for more information on the constructors. - [Breaking]
package config
has been moved to its own repository. seego.uber.org/config
for more information. fx.Lifecycle
has been added for modules to hook into the framework lifecycle events.service.Host
interface which composed a number of primitives together (configuration, metrics, tracing) has been deprecated in favor offx.App
.
1.0.0-beta3 - 2017-03-28
- [Breaking] Environment config provider was removed. If you were using environment variables to override YAML values, see config documentation for more information.
- [Breaking] Simplify Provider interface: remove
Scope
method from theconfig.Provider
interface, one can use either ScopedProvider and Value.Get() to access sub fields. - Add
task.MustRegister
convenience function which fails fast by panicking Note that this should only be used during app initialization, and is provided to avoid repetetive error checking for services which register many tasks. - Expose options on task module to disable execution. This will allow users to enqueue and consume tasks on different clusters.
- [Breaking] Rename Backend interface
Publish
toEnqueue
. Created a newExecuteAsync
method that will kick off workers to consume tasks and this is subsumed by module Start. - [Breaking] Rename package
uhttp/client
touhttp/uhttpclient
for clarity. - [Breaking] Rename
PopulateStruct
method in value toPopulate
. The method can now populate not only structs, but anything: slices, maps, builtin types and maps. - [Breaking]
package dig
has moved fromgo.uber.org/fx/dig
to a new home atgo.uber.org/dig
. - [Breaking] Pass a tracer the
uhttp/uhttpclient
constructor explicitly, instead of using a global tracer. This will allow to use http client in parallel tests.
1.0.0-beta2 - 2017-03-09
- [Breaking] Remove
ulog.Logger
interface and expose*zap.Logger
directly. - [Breaking] Rename config and module from
modules.rpc
tomodules.yarpc
- [Breaking] Rename config key from
modules.http
tomodules.uhttp
to match the module name - [Breaking] Upgrade
zap
tov1.0.0-rc.3
(now go.uber.org/zap, was github.com/uber-go/zap) - Remove now-unused
config.IsDevelopmentEnv()
helper to encourage better testing practices. Not a breaking change as nobody is using this func themselves according to our code search tool. - Log
traceID
andspanID
in hex format to match Jaeger UI. Upgrade Jaeger to min version 2.1.0 and use jaeger's adapters for jaeger and tally initialization. - Tally now supports reporting histogram samples for a bucket. Upgrade Tally to 2.1.0
- [Breaking] Make new module naming consistent
yarpc.ThriftModule
toyarpc.New
,task.NewModule
totask.New
- [Breaking] Rename
yarpc.CreateThriftServiceFunc
toyarpc.ServiceCreateFunc
as it is not thrift-specific. - Report version metrics for company-wide version usage information.
- Allow configurable service name and module name via service options.
- DIG constructors now support returning a tuple with the second argument being an error.
This is the first beta release of the framework, where we invite users to start building services on it and provide us feedback. Warning we are not promising API compatibility between beta releases and the final 1.0.0 release. In fact, we expect our beta user feedback to require some changes to the way things work. Once we reach 1.0, we will provider proper version compatibility.