docs(grid): filtering no longer uses activator.createinstance()

Author: marin-bratanov

components/grid/columns/bound.md

@@ -96,11 +96,15 @@ You can use the following properties on the bound columns:
     * If a `Field` is not set the column will not allow filtering, grouping, sorting and editing for the column.
     * If the `Field` points to a custom object or something like an `IDictionary`, errors will be thrown upon those actions because there are no known data operations on non-primitive types in .NET. An alternative is to implement all data source operations yourself by handling the [OnRead event](../manual-operations).
     * To bind to nested (complex) models (also called navigation properties), use only the name of the field that holds the child class and its own field. For an example, see the [Bind to navigation properties in complex objects]({%slug grid-use-navigation-properties%}) article.
+
 * The grid skips fields marked with the [`IgnoreDataMemberAttribute`](https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.ignoredatamemberattribute) when performing CUD operations. Its presence indicates that this property does not need to be part of the serialized data anyway, and skipping such fields allows [Lazy Loading Proxies in EF](https://docs.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.proxiesextensions.uselazyloadingproxies?view=efcore-3.1) to work.
+
 * If you don't set a `Title` for a column, the grid will take the `[Display(Name = "My Column Title")]` data annotation attribute from the model field. If that's not available either, the name of the field will be shown.
+
 * If you want to prevent data mutation for a specific property you can set the `Editable` parameter of the GridColumn or the `[Editable]` data annotation attribute to `false` for the desired model field.
- * Columns generated out of model properties that do not have a `setter` or it is not accessible (private) will not be editable too.
-* The Grid uses `Activator.CreateInstance<TItem>();` to generate a new item when an Insert or Filter action is invoked, so the Model should have a Parameterless constructor defined. A workaround for Insert operations might be [invoking them through the grid state]({%slug grid-state%}#initiate-editing-or-inserting-of-an-item) and creating the object with your own code.
+    * Columns generated out of model properties that do not have a `setter` or it is not accessible (private) will not be editable too.
+
+* The Grid uses `Activator.CreateInstance<TItem>();` to generate a new item when an Insert action is invoked, so the Model should have a Parameterless constructor defined. A workaround might be [invoking Insert through the grid state]({%slug grid-state%}#initiate-editing-or-inserting-of-an-item) and creating the object with your own code.
 
 
 >tip You can optimize database queries in two ways:

components/grid/editing/overview.md

@@ -191,7 +191,7 @@ There are a few considerations to keep in mind with the CUD operations of the gr
 
 * The CRUD event handlers must be `async Task` and **not** `async void`. A Task can be properly awaited and allows working with services and contexts. When the method returns `void`, the execution of the context operations is not actually awaited, and you may get errors from the context (such as "Cannot access a disposed object. A common cause of this error is disposing a context that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application" or "A second operation started on this context before a previous operation completed. This is usually caused by different threads using the same instance of DbContext").
 
-* The Grid uses `Activator.CreateInstance<TItem>();` to generate a new item when an Insert or Filter action is invoked, so the Model should have a Parameterless constructor defined. A workaround for Insert operations might be [invoking them through the grid state]({%slug grid-state%}#initiate-editing-or-inserting-of-an-item) and creating the object with your own code.
+* The Grid uses `Activator.CreateInstance<TItem>();` to generate a new item when an Insert action is invoked, so the Model should have a Parameterless constructor defined. A workaround might be [invoking Insert through the grid state]({%slug grid-state%}#initiate-editing-or-inserting-of-an-item) and creating the object with your own code.
 
 ## See Also