Notes update

Author: JasonBock

docs/notes/24 - Provide Filtering Capabilities.md

@@ -16,7 +16,7 @@
 * DONE - Get rid of `SearchForExtensionMethods` and related implementation. Let the compiler tell the user if there is a conflict, which is what this switch is trying to do. There's no point in having the generator do that work.
 * DONE - Add tests for attribute
 * DONE - Pass data through model and use it during code gen
-* Add filtering tests
+* DONE - Add filtering tests
     * DONE - Unit
         * DONE - Auto
         * DONE - TargetAuto
@@ -26,5 +26,5 @@
     * DONE - Integration
         * DONE - Auto
         * DONE - TargetAuto
-* What happens if you add the attribute more than once with different filtering characteristics?
-* What happens if you put a property name in the filter list, and that property by name does not exist on the target type?
+* DONE - What happens if you add the attribute more than once with different filtering characteristics? Can't happen with `[AutoDeconstruct]` as that is one per type, if it's done with `[TargetAutoDeconstruct]`, a compiler error will occur as two files will have the same on generation.
+* DONE - What happens if you put a property name in the filter list, and that property by name does not exist on the target type? Use a `HashSet<string>` to ensure uniqueness, and then if