Dip changelog

Changelog History

Page 2

• v5.0.1 Changes

  September 16, 2016

  🚀 This release is the same as 5.0.0 and only fixes CocoaPods speck pushed to trunk without macOS, tvOS and watchOS deployment targets. Please use this release instead of 5.0.0 if you integrate Dip via Cocoapods.

• v5.0.0 Changes

  • Migrated to Swift 3.0
    #120, @patrick-lind, @mark-urbanthings, @ilyapuchka
  • 🔨 Renamed DefinitionOf to Definition and some other source-breaking refactoring.
    #113, @ilyapuchka
  • ➕ Added invalidType error when resolved instance does not implement requested type.
    #118, @ilyapuchka
  • ➕ Added optional type parameter in register methods to be able to specify type when registering using method literal instead of closure. #115, @ilyapuchka
  • ➕ Added implements family of methods in to Definition to register type-forwarding definitions.
    #114, @ilyapuchka
  • 0️⃣ Shared scope is now the default scope.
    #112, @ilyapuchka
  • Single target project setup.
    #121, @ilyapuchka
  • Simplified implementation of auto-wiring.
    #117, @ilyapuchka

  🛠 Fixed

  • Auto-injected properties inherited from super class are now properly injected when resolving subclass. ➕ Added resolveDependencies(_:DependencyContainer) method to Resolvable protocol to handle inheritance when resolving.
    #116, @ilyapuchka

• v4.6.1 Changes

  🛠 Fixed

  • 🛠 Fixed sharing singletons between collaborating containers.
    #103, @ilyapuchka
  • 🚀 Renamed some public API's (see release notes for more info).
    #105, @ilyapuchka

• v4.6.0 Changes

  • Containers collaboration. Break your definitions in modules and link them together.
    #95, @ilyapuchka
  • ➕ Added WeakSingleton scope.
    #96, @ilyapuchka
  • Properties Auto-injection now is performed before calling resolveDependencies block
    #97, @ilyapuchka
  • 🛠 Fixed updating container's context when resolving properties with auto-injection.
    #98, @ilyapuchka
  • 👌 Improved logging.
    #94, #99, @ilyapuchka
  • 🛠 Fixed warning about using only extensions api.
    #92, @mwoollard

• v4.5.0 Changes

  • ➕ Added weakly-typed API to resolve components when exact type is unknown during compile time.
    #79, @ilyapuchka
  • ➕ Added type forwarding feature. You can register the same factory to resolve different types.
    #89, @ilyapuchka
  • Container now can resolve optional types :tada:
    #84, @ilyapuchka
  • ➕ Added container context that provides contextual information during graph resolution process.
    #83, @ilyapuchka
  • ➕ Added method to validate container configuration.
    #87, @ilyapuchka
  • ➕ Added method to manually set value wrapped by auto-injection wrappers.
    #81, @ilyapuchka
  • ➕ Added separate error type for failures during auto-wiring.
    #85, @ilyapuchka

• v4.4.0 Changes

  • ➕ Added .EagerSingleton scope for objectes requiring early instantiation and bootstrap() method on DepenencyContainer.
    #65, @ilyapuchka
  • ⏪ Reverted order of Resolvable callbacks.
    #67, @ilyapuchka

• v4.3.1 Changes

  • 🛠 Fix Swift 2.2 compile errors in tests.
    #62, @mwoollard

• v4.3.0 Changes

  • ➕ Added DependencyTagConvertible protocol for better typed tags.
    #50, @gavrix
  • Auto-wiring. DependencyContainer resolves constructor arguments automatically.
    #55, @ilyapuchka
  • ➕ Added Resolvable protocol to get a callback when dependencies graph is complete.
    #57, @ilyapuchka
  • ✂ Removed DipError.ResolutionFailed error for better consistency.
    #58, @ilyapuchka

• v4.2.0 Changes

  • ➕ Added support for Swift Package Manager.
    #41, @ilyapuchka
  • ➕ Added Linux support.
    #42, #46, @ilyapuchka
  • 🛠 Fixed the issue that could cause singleton instances to be reused between different containers.
    #43, @ilyapuchka
  • ➕ Added public AutoInjectedPropertyBox protocol for user-defined auto-injected property wrappers.
    #49, @ilyapuchka

• v4.1.0 Changes

  🆕 New features

  • ➕ Added auto-injection feature.
    #13, @ilyapuchka
  • Factories and resolveDependencies blocks of DefinitionOf are now allowed to throw. Improved errors handling.
    #32, @ilyapuchka
  • 👍 Thread safety reimplemented with support for recursive methods calls.
    #31, @mwoollard

• « First
• ‹ Prev
• 1
• 2
• 3
• 4
• Next ›
• Last »