Skip to content

Commit

Permalink
fix: remove .html on internal link
Browse files Browse the repository at this point in the history
  • Loading branch information
Romakita committed Mar 6, 2024
1 parent 0db58f4 commit 3e23364
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/docs/pipes.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ The goal of validation use case is to ensure that the input parameter is valid b

Officially, Ts.ED has two way to declare a @@JsonShema@@ validation:

- With [model](/doc/model.html) decorators,
- With [model](/docs/model) decorators,
- With @@UseSchema@@ decorator, it's a decorator Pipe provided by @tsed/ajv package.

We'll take the model declaration to explain the Validation pipe use case. Let's focus on the `PersonModel`:
Expand Down Expand Up @@ -155,7 +155,7 @@ and throw an exception when the payload is not valid.
The validation pipe is a very specific use case because Ts.ED uses it automatically when a parameter is handled
by the **routing request**. The previous pipe example, in order to work, needs to be registered with the @@OverrideProvider@@ decorator instead of @@Injectable@@.

See more details on the [validation page](/docs/validation.html).
See more details on the [validation page](/docs/validation).

## Transformation use case

Expand Down Expand Up @@ -186,7 +186,7 @@ This is useful when you have to get data from **database** based on an input dat
Given this `PersonModel`:

```typescript
import { MinLength, Required } from "@tsed/common";
import { MinLength, Required, Property } from "@tsed/common";

class PersonModel {
@Property()
Expand Down

0 comments on commit 3e23364

Please sign in to comment.