Overview

Domain Rules#

Rules LS1001 to LS1013 run in Domain only.

• LS1001: Domain References an Outer-Layer Concern: reports a Domain use of an outer-layer namespace.
• LS1002: Domain Declares an Enum: reports an enum declared in Domain.
• LS1003: Aggregate Has No State Record: reports an aggregate with no State record.
• LS1004: State Case Is Not Sealed: reports a state case that is not sealed.
• LS1005: Domain Throws a Non-Domain Exception: reports a throw of a non-DomainException type.
• LS1006: Domain Exception Is Misnamed or Open: reports a DomainException subclass that is misnamed or open.
• LS1007: Domain Event Is Not an Immutable Record: reports a domain event that is not an immutable record.
• LS1008: Domain Uses Binary Floating Point: reports a double or float use.
• LS1009: Domain Reads a Nondeterministic Value: reports a read of the clock, randomness, or a new identifier.
• LS1010: Repository Exposes a Query Surface: reports a repository that exposes a query surface.
• LS1011: Public Domain Contract Is Undocumented: reports a public contract without XML documentation.
• LS1012: Identifier Is Not a Strongly Typed Value: reports an identifier that is not a strongly typed value.
• LS1013: Switch Leaves a Sealed Case to Its Discard Arm: reports a switch that leaves a sealed case to its discard arm.

Outer-Layer Rules#

Rules LS2001, LS2003 to LS2007, and LS2009 to LS2020 run across layers, as each page states.

• LS2001: Implementation Type Is Not Internal Sealed: reports an implementation type that is not internal sealed.
• LS2003: WebApi Uses an MVC Controller: reports an MVC controller.
• LS2004: Command Handler Writes Through a Document Session: reports a command handler that writes through a session.
• LS2005: Handler Name Lacks Its Command or Query Suffix: reports a handler whose name lacks its command or query suffix.
• LS2006: Endpoint Name Lacks Its Suffix: reports an endpoint whose name does not end in Endpoint.
• LS2007: Reaction or Job Name Hides Its Kind: reports a reaction or job whose name hides its kind.
• LS2009: Result Part Not Named After Its Result: reports a result part not named after its result.
• LS2010: Repository Variable Not Named After Its Interface: reports a repository variable not named after its interface.
• LS2011: Query Handler Takes a Repository: reports a query handler that takes a repository.
• LS2012: Handler Authorizes Itself: reports a handler that throws a forbidden refusal.
• LS2013: Audit Value Read from the Message in the Handler: reports an audit value read from the message in the handler.
• LS2014: Command Handler Finds or Creates: reports a command handler that finds or creates.
• LS2015: Command Handler Changes Records in a Loop: reports a command handler that changes records in a loop.
• LS2016: Handler Takes a Pipeline-Owned Collaborator: reports a handler that takes a pipeline-owned collaborator.
• LS2017: LiteSpecLayer Names No Known Layer: reports a declared layer value that names no known layer.
• LS2018: File Names a Type Outside Its Layer: reports a type outside the file's layer.
• LS2019: Use Case Names a Type of Another Use Case: reports a type declared in another use case, reaction, or job folder.
• LS2020: Module Names a Type Outside Another Module's Contracts: reports a type of another module declared outside its Contracts folder.

Naming and Style Rules#

Rules LS3001 and LS3004 run in every production layer.

• LS3001: Asynchronous Method Name Lacks Async: reports an async method name without Async.
• LS3004: Concrete Class Is Not Sealed: reports a concrete leaf class that is not sealed.

Test Rules#

Rule LS4001 runs in test projects only.

• LS4001: Test Contains No Assertion: reports a test method with no assertion.

Traceability Rules#

Rules LS5001 to LS5009, LS5011, and LS5012 run across layers, as each page states.

• LS5001: Code Element Carries No Mark: reports a code element of a recognized kind with no mark.
• LS5002: Mark Names No Usable Record: reports a mark naming no record, or a record of a type its element does not take.
• LS5003: Code Element Carries the Wrong Number of Marks: reports a code element with more or fewer marks than its kind takes.
• LS5004: Mark Uses the Undeclared Style: reports a mark written in the style the project did not declare.
• LS5005: Runtime Value Differs from Its Record: reports a hand-written event Classification or exception Code differing from its record.
• LS5006: Marked Event or Exception Is Not Partial: reports a marked domain event or rule exception that is not partial.
• LS5007: Marked Act Raises an Undeclared Event: reports a marked method raising an event its use case does not list.
• LS5008: Declared Event Is Raised by No Marked Act: reports a listed event no method marked with its use case raises.
• LS5009: Two Permissions Generate One Constant Name: reports two permission records whose names generate the same constant.
• LS5011: One Message Maps to Two Use Cases: reports a message two marked handlers serve with different use cases.
• LS5012: Role Allows an Undeclared Permission: reports a role whose record allows a permission no record declares.