0.12.0
Breaking Changes
Marking soon to be removed methods in the fluent api as obsolete by @brandhuf in #362
Until now, ArchUnitNET provided overloads of functions in the fluent syntax that took a string as an argument like Types().That().DependOnAny("ExampleClass") or Types().That().DependOnAny(".*ExampleClass", true). Here, however, it is unclear whether the string would match the Name, FullName or AssemblyQualifiedName. These functions have now been marked as obsolete and will be removed in version 0.13.0.
Besides HaveName, the fluent interface now also provides the functions HaveNameMatching, HaveFullName and HaveFullNameMatching. The above call can therefore be replaced with Types().That().DependOnAny(Types().That().HaveName("ExampleClass")) or Types().That().DependOnAny(Types().That().HaveFullNameMatching(".*ExampleClass")), giving a clear indication of what is matched and how it is matched.
Don't Set Assembly Name To It's Full Name by @alexanderlinne in #372
This is a bug where the Name of an assembly was always set to its FullName. This may be a breaking change for code that currently relies on this behaviour.
Fixes
- Fix Check in AreNotReadOnly Predicate by @alexanderlinne in #373
Enhancements
- Reduce Code Duplication in Fluent Syntax Object Conditions by @alexanderlinne in #367
Dependency Updates
Full Changelog: 0.11.4...0.12.0