Factory 2.1.0 Released

[hmlongco]

2.1.0

Factory 2.1 has a set of exciting new features that include...

• Contexts allow quick and easy Factory customization when doing previews, debugging and testing.
• Provides once modifier which allows one-time initialization on a per-Factory basis.
• Let's you define the default scope used for a given container.
• Allows you to specify promised optionals that warn when registrations are not provided.
• Singletons now span containers and are cached separately.
• Factory library now implemented across multiple files.

As mentioned in another post, one of the tentpole features in 2.1 is contexts...

Contexts

Once reason Factory 2.0 leaned heavily into the modifier syntax is that I knew this feature was coming. Now I'm happy to announce it!

Developers often use Factory to mock data for previews and unit tests. Now Factory 2.1 extends these capabilities by allowing them to easily specify dependencies based on the application's current context.

What if, for example, you never want your application's analytics library to be called when running unit tests?

Piece of cake. Just register a new factory closure for that service whenever it runs in that particular context.

container.analytics
      .onTest { StubAnalyticsEngine() }

Factory provides a variety of contexts for testing, debugging, previews, simulator, device, and for checking passed parameters when running UI tests and checking builds on services like BrowserStack.

As an example of the later:

myServiceType
    .onArg("mock0") { EmptyService() }
    .onArg("mock1") { MockServiceN(1) }
    .onArg("error") { MockError(404) }

Now you can have a single build change its behavior based on passed parameters.