UNPKG

@loopback/docs

Version:

Documentation files rendered at [https://loopback.io](https://loopback.io)

github.com/loopbackio/loopback-next/tree/master/docs

loopbackio/loopback-next

37 lines (29 loc) • 1.56 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
--- lang: en title: 'Validation' keywords: LoopBack 4.0, LoopBack 4, Node.js, TypeScript, OpenAPI sidebar: lb4_sidebar permalink: /doc/en/lb4/Validation.html --- Within a LoopBack application, validation can be added in various places depending on the usage. Some types of validations come out-of-the-box in LoopBack, such as type validation in the REST layer, whereas some require additional configuration or code. There are various types of validations such as: - validation of input/output for method invocations - validation of model instance properties, for example, age < 0 - validation of model collections, for example, uniqueness Let's take a closer look at how validation can be added in the following layers: - [REST layer](Validation-REST-layer.md) - [Controller, Repository and Service Layer](Validation-controller-layer.md) - [ORM layer](Validation-ORM-layer.md) The [validation-app example application](https://github.com/loopbackio/loopback-next/blob/master/examples/validation-app) is used in the following documentation pages for demonstration. In the example, a `CoffeeShop` model is being used. It has the following properties. | Property name | Type | Description | | ------------- | :----: | ------------------------------------- | | shopId | string | ID of the coffee shop | | city | string | City where the coffee shop is located | | phoneNum | string | Phone number of the coffee shop | | capacity | number | Capacity of the coffee shop |