diff --git a/docs/modeling/model-components/data-sources.md b/docs/modeling/model-components/data-sources.md index 32d053060..77546359d 100644 --- a/docs/modeling/model-components/data-sources.md +++ b/docs/modeling/model-components/data-sources.md @@ -9,7 +9,7 @@ In addition to this standard data source, Coalesce allows you to create custom d By default, each of your models that Coalesce exposes will expose the standard data source (`IntelliTect.Coalesce.StandardDataSource`). This data source provides all the standard functionality one would expect - paging, sorting, searching, filtering, and so on. Each of these component pieces is implemented in one or more virtual methods, making the `StandardDataSource` a great place to start from when implementing your own data source. To suppress this behavior of always exposing the raw `StandardDataSource`, create your own custom data source and annotate it with `[DefaultDataSource]`. -To implement your own custom data source, you simply need to define a class that implements `IntelliTect.Coalesce.IDataSource`. To expose your data source to Coalesce, either place it as a nested class of the type `T` that you data source serves, or annotate it with the `[Coalesce]` attribute. Of course, the easiest way to create a data source that doesn't require you to re-engineer a great deal of logic would be to inherit from `IntelliTect.Coalesce.StandardDataSource`, and then override only the parts that you need. +To implement your own custom data source, you simply need to define a class that implements `IntelliTect.Coalesce.IDataSource`. To expose your data source to Coalesce, either place it as a nested class of the type `T` that your data source serves, or annotate it with the `[Coalesce]` attribute. Of course, the easiest way to create a data source that doesn't require you to re-engineer a great deal of logic would be to inherit from `IntelliTect.Coalesce.StandardDataSource`, and then override only the parts that you need. ``` c# public class Person