update readme

Author: NeVeSpl

README.md

@@ -1,16 +1,16 @@
 # NetArchTest.eNhancedEdition
 
-A fluent API for .Net Standard that can enforce architectural rules in unit tests. 
+A fluent API for .Net Standard that can enforce architectural rules in unit tests and create a *self-testing architecture*. Inspired by the [ArchUnit](https://www.archunit.org/) library for Java.
 
-Inspired by the [ArchUnit](https://www.archunit.org/) library for Java.
+NetArchTest.eNhancedEdition is based on [NetArchTest v1.3.2](https://github.com/BenMorris/NetArchTest). If you are not familiar with NetArchTest, you should start by reading [introduction on Ben's blog](https://www.ben-morris.com/writing-archunit-style-tests-for-net-and-c-for-self-testing-architectures).
 
 ## Rationale
 
-This project allows you create tests that enforce conventions for class design, naming and dependency in .Net code bases. These can be used with any unit test framework and incorporated into a build pipeline. It uses a fluid API that allows you to string together readable rules that can be used in test assertions.
 
-There are plenty of static analysis tools that can evaluate application structure, but they are aimed more at enforcing generic best practice rather than application-specific conventions. The better tools in this space can be press-ganged into creating custom rules for a specific architecture, but the intention here is to incorporate rules into a test suite and create a *self-testing architecture*.
 
-The project is inspired by [ArchUnit](https://www.archunit.org/), a java-based library that attempts to address the difficulties of preserving architectural design patterns in code bases over the long term. Many patterns can only be enforced by convention, which tends to rely on a rigorous and consistent process of code review. This discipline often breaks down as projects grow, use cases become more complex and developers come and go. 
+## Getting started
+
+The library is available as a package on NuGet: [NetArchTest.eNhancedEdition](https://www.nuget.org/packages/NetArchTest.eNhancedEdition/).
 
 ## Examples
 
@@ -20,33 +20,23 @@ var result = Types.InCurrentDomain()
     .That()
     .ResideInNamespace("NetArchTest.SampleLibrary.Presentation")
     .ShouldNot()
-    .HaveDependencyOn("NetArchTest.SampleLibrary.Data")
-    .GetResult()
-    .IsSuccessful;
-
-// Classes in the "data" namespace should implement IRepository
-result = Types.InCurrentDomain()
-    .That().HaveDependencyOn("System.Data")
-    .And().ResideInNamespace(("ArchTest"))
-    .Should().ResideInNamespace(("NetArchTest.SampleLibrary.Data"))
+    .HaveDependencyOnAny("NetArchTest.SampleLibrary.Data")
     .GetResult()
     .IsSuccessful;
 
 // All the service classes should be sealed
-result = Types.InCurrentDomain()
-    .That().ImplementInterface(typeof(IWidgetService))
-    .Should().BeSealed()
+var result = Types.InCurrentDomain()
+    .That()
+    .ImplementInterface(typeof(IWidgetService))
+    .Should()
+    .BeSealed()
     .GetResult()
     .IsSuccessful;
 ```
 
-## Getting started
-
-The main rules library is available as a package on NuGet: [NetArchTest.Rules](https://www.nuget.org/packages/NetArchTest.Rules/).
 
-It is a .Net Standard 2.0 library that is compatible with .Net Framework 4.6.1 or better and .Net Core 2.0 or better.
 
-### Writing rules
+## Writing rules
 
 The fluent API should direct you in building up a rule based on a combination of predicates, conditions and conjunctions. 
 
@@ -68,49 +58,24 @@ Finally, you obtain a result from the rule by using an executor, i.e. use `GetTy
 var isValid = types.That().ResideInNamespace(“MyProject.Data”).Should().BeSealed().GetResult().IsSuccessful;
 ```
 
-### Custom rules
+
+## Dependencies 
+
+## Slices 
+
+## Custom rules
 
 You can extend the library by writing custom rules that implement the `ICustomRule` interface. These can be applied as both predicates and conditions using a `MeetsCustomRule()` method, e.g.
 
 ```csharp
 var myRule = new CustomRule();
 
 // Write your own custom rules that can be used as both predicates and conditions
-result = Types.InCurrentDomain()
-    .That().AreClasses()
+var result = Types.InCurrentDomain()
+    .That()
+    .AreClasses()
     .Should()
     .MeetCustomRule(myRule)
-    .GetResult().IsSuccessful;
-```
-
-### Grouping rules into Policies
-
-Rules can be grouped into policies using the fluent interface exposed by the `Policy` class, e.g. 
-
-```csharp
-var architecturePolicy = Policy.Define("Example Policy", "This is an example policy")
-                .For(Types.InCurrentDomain)
-                .Add(t =>
-                   t.That()
-                   .ResideInNamespace("NetArchTest.SampleLibrary.Presentation")
-                   .ShouldNot()
-                   .HaveDependencyOn("NetArchTest.SampleLibrary.Data"),
-                   "Enforcing layered architecture", "Controllers should not directly reference repositories"
-                )
-                ...
-                .Add(t =>
-                    t.That()
-                    .AreInterfaces()
-                    .Should()
-                    .HaveNameStartingWith("I"),
-                    "Generic implementation rules", "Interface names should start with an 'I'"
-                );
-
-```
-The rules are loaded lazily and executed when the `Evaluate()` method is called. This method returns a `PolicyResults` instance that can be passed to a reporting mechanism.
-
-The [ExamplePolicies](https://github.com/BenMorris/NetArchTest/blob/master/samples/NetArchTest.SampleRules/ExamplePolicies.cs) class in the samples demonstrates how to do this.
-
-## Further reading
-
-A more extensive blog post describing the implementation detail is available in [my blog](https://www.ben-morris.com/writing-archunit-style-tests-for-net-and-c-for-self-testing-architectures).
+    .GetResult()
+    .IsSuccessful;
+```

src/NetArchTest.Rules/PredicateList.cs

@@ -60,7 +60,7 @@ internal IEnumerable<TypeSpec> GetTypeSpecifications()
         }
         internal IEnumerable<Type> GetNetTypes()
         {
-            return GetTypes().Select(x => x.Type);
+            return GetTypeSpecifications().Select(x => x.Definition.ToType());
         }
 
         /// <summary>