Releases: TNG/ArchUnitNET
Fix for loading managed C++ Projects
Thankfully, @ivsavchenko provided a fix for a bug which prevented some managed C++ dependencies from loading.
Contributors
Assets 2
PlantUML
Another performance improvement
This release improves the performance when evaluation conditions, which behaved quadratically and thus was problematic when evaluation a large number of items.
Improve performance for loading architectures
This release fixes a performance issue that types where loaded multiple times. This should speed up the tests significantly.
Filtering for LoadAssembliesRecursively
Added a filter parameter to LoadAssembliesRecursively, to be able to allow finegrained control which packages are loaded into ArchUnit.
new ResideInAssembly overload
ResideInAssembly now also supports the Assembly objects from the Domain namespace as input parameters
API-Cleanup and bugfixes
Note: in this release we bundled some breaking changes to fix some API inconsistencies. We assume that there are no huge changes to your test code to be made, but you might encounter some breaking tests.
Breaking changes
- Always match names exactly, and optionally offer Regex-based matching (#145)
- Clean up some deprecated properties to get rid of some confusion: https://github.com/TNG/ArchUnitNET/pull/148/files
- Clean up of the IsAssignableTo and ImplementsInterface APIs: #154
Improvements
- Improved PlantUML-Diagram generation, the api for this feature is not expected to be stable now and might be extended soon
- Messages for failed test cases should be cleaner now
Bugfixes
Fix handling for Types not existing in the architecture: #156
Fix handling for generic types: #154
Fix support of generic types for HaveReturnType()
Minor Bugfix for the support of generic types for HaveReturnType()
Create distinct types for structs and enums
This release fixes a conceptual issue described in #96. Since there are some breaking changes to the fluent syntax, we bump to 0.9.0.
Proper handling of async methods
This release fixes #138, where dependencies of async methods were not properly handled