From b8b5f6eceb4428731f041bcc6232ca22dfe77bd5 Mon Sep 17 00:00:00 2001 From: Scott Addie Date: Tue, 5 Sep 2017 15:29:37 -0500 Subject: [PATCH] Add missing comma --- aspnetcore/data/ef-mvc/complex-data-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/data/ef-mvc/complex-data-model.md b/aspnetcore/data/ef-mvc/complex-data-model.md index e03e70c60184..6f8acfc0aacb 100644 --- a/aspnetcore/data/ef-mvc/complex-data-model.md +++ b/aspnetcore/data/ef-mvc/complex-data-model.md @@ -393,7 +393,7 @@ protected override void OnModelCreating(ModelBuilder modelBuilder) } ``` -In this tutorial you're using the fluent API only for database mapping that you can't do with attributes. However, you can also use the fluent API to specify most of the formatting, validation, and mapping rules that you can do by using attributes. Some attributes such as `MinimumLength` can't be applied with the fluent API. As mentioned previously, `MinimumLength` doesn't change the schema, it only applies a client and server side validation rule. +In this tutorial, you're using the fluent API only for database mapping that you can't do with attributes. However, you can also use the fluent API to specify most of the formatting, validation, and mapping rules that you can do by using attributes. Some attributes such as `MinimumLength` can't be applied with the fluent API. As mentioned previously, `MinimumLength` doesn't change the schema, it only applies a client and server side validation rule. Some developers prefer to use the fluent API exclusively so that they can keep their entity classes "clean." You can mix attributes and fluent API if you want, and there are a few customizations that can only be done by using fluent API, but in general the recommended practice is to choose one of these two approaches and use that consistently as much as possible. If you do use both, note that wherever there is a conflict, Fluent API overrides attributes.