Attributes

Coalesce provides a number of C# attributes that can be used to decorate your model classes and their properties in order to customize behavior, appearance, security, and more. Coalesce also supports a number of annotations from System.ComponentModel.DataAnnotations.

Coalesce Attributes

Visit each link below to learn about the attribute that Coalesce provides that can be used to decorate your models.

• [ClientValidation]
• [Coalesce]
• [Controller]
• [ControllerAction]
• [CreateController]
• [DateType]
• [DefaultOrderBy]
• [DtoIncludes] & [DtoExcludes]
• [Execute]
• [File]
• [Hidden]
• [Inject]
• [InternalUse]
• [ListText]
• [LoadFromDataSource]
• [ManyToMany]
• [Search]
• Security Attributes
• [SelectFilter]
• [TypeScriptPartial]

ComponentModel Attributes

Coalesce also supports a number of the built-in System.ComponentModel.DataAnnotations attributes and will use these to shape the generated code.

[Display]

The displayed name and description of a property, as well as the order in which it appears in generated views, can be set via the [Display] attribute. By default, properties will be displayed in the order in which they are defined in their class.

[DisplayName]

The displayed name of a property can also be set via the [DisplayName] attribute.

[Required]

Properties with [Required] will generate client validation rules. See [ClientValidation].

[Range]

Properties with [Range] will generate client validation rules. See [ClientValidation].

[MinLength]

Properties with [MinLength] will generate client validation rules. See [ClientValidation].

[MaxLength]

Properties with [MaxLength] will generate client validation rules. See [ClientValidation].

[ForeignKey]

Normally, Coalesce figures out which properties are foreign keys, but if you don't use standard EF naming conventions then you'll need to annotate with [ForeignKey] to help out both EF and Coalesce. See the Entity Framework Relationships documentation for more.

[InverseProperty]

Sometimes, Coalesce (and EF, too) can have trouble figuring out what the foreign key is supposed to be for a collection navigation property. See the Entity Framework Relationships documentation for details on how and why to use [InverseProperty].

[DatabaseGenerated]

Primary Keys with [DatabaseGenerated(DatabaseGeneratedOption.None)] will be settable on the client and will be appropriately handled by the Standard Behaviors on the server. Currently unsupported on the Knockout front-end stack.

[NotMapped]

Model properties that aren't mapped to the database should be marked with [NotMapped] so that Coalesce doesn't try to load them from the database when searching or carrying out the Default Loading Behavior.