From e3124b53e6d5a64cc79f770ebbac35eac5e04785 Mon Sep 17 00:00:00 2001 From: Mike Bierlee Date: Sat, 14 Jun 2014 00:05:47 +0200 Subject: [PATCH] Prepare release 0.1.1 --- CHANGES.md | 17 ++++++++++------- README.md | 4 ++-- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index 4468eeb..1e6fb0c 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -1,7 +1,10 @@ -Poodinis Changelog -================== -**Version 0.1** -* Initial open-source release -* ADD support for registering and resolving -* ADD registration scopes -* ADD autowiring +Poodinis Changelog +================== +**Version 0.1.1** +* FIX: Also auto-wire members from base classes + +**Version 0.1.0** +* Initial open-source release +* ADD support for registering and resolving +* ADD registration scopes +* ADD autowiring diff --git a/README.md b/README.md index ef080bc..61b5254 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ Poodinis Dependency Injection Framework ======================================= -Version 0.1 +Version 0.1.1 Copyright 2014 Mike bierlee Licensed under the terms of the MIT license - See [LICENSE.txt](LICENSE.txt) @@ -122,7 +122,7 @@ Poodinis can autowire circular dependencies when they are registered with single Known issues ------------ * Due to preventive measures of recursion issues in circular dependencies, registrations which are supposed to yield new instances will not autowire classes for which a circular dependency is detected. A new instance will be resolved but the instance's members will not be autowired. -* Resolving a class registered by supertype or interface will only autowire the members inherited from its supertype and in the case of interfaces nothing at all. +* Resolving a class registered by supertype or interface will only autowire the members inherited from its supertypes and in the case of interfaces none at all. Future Work -----------