All Versions
18
Latest Version
Avg Release Cycle
41 days
Latest Release
1731 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v1.0.7 Changes
June 19, 2020 -
v1.0.6 Changes
June 11, 2020 -
v1.0.5 Changes
May 18, 2020 -
v1.0.4 Changes
May 11, 2020 -
v1.0.3 Changes
February 24, 2020 -
v1.0.2 Changes
January 27, 2020 -
v1.0.1 Changes
December 20, 2019New Features
- Parameters can use
weak
orcontainer
scopes [#90] - ๐ง Closure configuration attribute in order to handle dependency with a closure type [#108]
๐ Bug Fixes
- ๐ Fixed input file listing which was blocking Weaver when trying to use (unsupported) wildcards.
- ๐ Fixed type parser edge cases.
- Parameters can use
-
v1.0.0 Changes
December 15, 2019๐ฑ First stable version of Weaver ๐
Foundations rework
- Dependency Graph: The dependency graph representation has been entirely reworked in order to allow for more flexibility at use. Basically, it is now linked using hash keys rather than direct object references.
- ๐ Linker/Inspector: Since the dependency graph changed, the linker & Inspector naturally changed as well. Accessing to data through the graph can now throw, giving a more precise error handling. The visitor algorithm for resolving and building remains fairly the same, but now supports new features, which I will describe a bit below.
- ๐ Generator: The generator has been entirely rewritten using Meta. It also supports new features which I will describe below.
Optimizations
- โก๏ธ Lexer: A cache (
LexerCache
) has been added in order to avoid SourceKitten to parse the source files every time (~1s for ~30 files). This cache stores one token list per file. A token list is invalidated once its file has changed after it was stored. The format for storing is an optimized JSON where every key is only one or two characters. - ๐ Generator: The generated Swift code is now relying a lot more on runtime, which brings more flexibility for supporting new features, but also allows Weaver to generate one single dependency container per project instead of one per injectable type
- Misc optimizations as a result of profiling the binary (~0.5s instead of ~2s for ~30 files when cache is complete).
๐ New Features
- ๐ Property wrapper support. With Swift 5.1, Weaver is now able to detect property wrappers named
@Weaver(...)
as annotations. - Dependencies can now be resolved by name and/or by type.
- Abstract types can be composite (eg.
A & B
) and still be resolved correctly as soon as a registration is declared up the tree with a super set abstract type (eg.A & B & C
). - Some new (more specific) errors are now thrown. Eg. type mismatch, ambiguous type, ambiguous dependency name, etc...
- โ Added generation of a stub implementation of the main dependency resolver to facilitate testing. The code is generated in a separated file
WeaverTests.swift
. - โ Added scope
lazy
which activates a lazy loading mechanism for a given dependency. - โ Added configuration attribute
setter
which makes Weaver generate a setter for a given dependency. - An injectable type can now reference itself. The stored reference is weak, avoiding retain cycles. The optionality of that reference is abstracted away by Weaver though.
๐ฅ Breaking changes
- โ Only one unique file per target (app/tests) can be generated while Weaver used to offer an option to generate multiple files.
- ๐ Naturally, the
xcfilelist
command has been removed since its necessity was very limited by the fact that only one file is generated now. - Detailed resolvers are always on, which means the option doesn't exist anymore.
- ๐ Custom stencil templates aren't supported anymore, since Stencil has been replaced by Meta.
-
v0.12.3 Changes
April 12, 2019 -
v0.12.2 Changes
February 21, 2019- ๐ Fixed
--single-output
option (#101). - ๐ Fixed
make install
command.
- ๐ Fixed