
//entity
class OrderLine(
val sku: String,
val price: Int,
val count: Int
) {
init {
//an invariant guarded where the data is born
require(count > 0) { "bad count" }
}
val cost: Int
get() = price * count
}
//entity
class Order(val id: Int) {
private val lines = mutableListOf<OrderLine>()
//only the entity itself may flip the flag
var paid: Boolean = false
private set
val size: Int
get() = lines.size
val total: Int
get() = lines.sumOf { it.cost }
//business rule: 10% off from 200
val discount: Int
get() = if (total >= 200) total / 10 else 0
val payable: Int
get() = total - discount
//business rule: a paid order is closed for changes
fun add(sku: String, price: Int, count: Int) {
check(!paid) { "order already paid" }
lines.add(OrderLine(sku, price, count))
}
//business rule: an empty order is never paid
fun pay() {
check(lines.isNotEmpty()) { "empty order" }
paid = true
}
}
//client code
//no database and no screen anywhere above
val order = Order(1001)
order.add("pen", 30, 2)
order.add("lamp", 190, 1)
println("order ${order.id}")
println("lines ${order.size}")
println("total ${order.total}")
println("discount ${order.discount}")
println("payable ${order.payable}")
order.pay()
println("paid ${order.paid}")
//the entity guards its own state, not a screen
try {
order.add("pen", 30, 1)
} catch (error: IllegalStateException) {
println("refused: ${error.message}")
}
//a smaller order stays under the discount rule
val small = Order(1002)
small.add("pen", 30, 1)
println("order ${small.id}")
println("total ${small.total}")
println("discount ${small.discount}")
//the rules refuse bad data, and nobody else has to
try {
small.add("chair", 30, 0)
} catch (error: IllegalArgumentException) {
println("refused: ${error.message}")
}
try {
Order(1003).pay()
} catch (error: IllegalStateException) {
println("refused: ${error.message}")
}
//printed: order 1001
// lines 2
// total 250
// discount 25
// payable 225
// paid true
// refused: order already paid
// order 1002
// total 30
// discount 0
// refused: bad count
// refused: empty order
An entity holds a business rule of the shop and knows nothing about a database, a screen or the network, so it can be tested without them.Read moreThe problem. A shop gives 10% off every order from 200. If this rule lives in a web page, and again in a database query, the two copies soon disagree. To check the rule, you must start the page or the database. The most important knowledge of the shop is scattered and hard to test. The idea. An entity is a piece of data together with the business rules about it: what an order contains, how its total is counted, when it may be paid. It knows nothing about a database, a screen or the network. Clean architecture has one main rule, the dependency rule: outer code may know inner code, but inner code never knows outer code. Entities are the innermost code, so they depend on nothing. How to read the example. There are two entities: a line of an order and the order itself. The order sums its lines, gives 10% off from 200 and counts the amount to pay. It refuses to be paid while it is empty. The client code builds order 1001 with two lines and prints its numbers: the total is 250, the discount 25 and the amount to pay 225. It also tries to pay an empty order, and the entity refuses. In some languages the entity is a plain value with functions, not a class; its role is the same. When to use it. Make an entity for each concept of the business that has its own rules, such as an order or an account. Data without rules needs no entity: a simple structure is enough. A common mistake. An entity that saves itself to the database or formats itself for the screen. Then it depends on outer code, and its rules can no longer be tested alone. |