# Tip - Serialization

When discussing **serialization**, in the sense of altering the <mark style="color:blue;">`response`</mark> returned (hide <mark style="color:blue;">`password`</mark>, bring order's <mark style="color:blue;">`total`</mark>), this is something that Prisma still does not excel, let's say. To achieve this currently is not trivial, some alternatives are:

* Create an **entity** that reflects the model and uses **class transformer** decorators (<mark style="color:red;">code duplication</mark>)
* Use an **interceptor** to analyse the response and alter it as necessary(<mark style="color:red;">bad performance</mark>)

But none of these is particularly ideal. Recently, Prisma has received a preview <mark style="color:blue;">`omit`</mark> option when fetching entities. Still not ideal but at least it is a bit better. Does not cover all cases but we could use it in the <mark style="color:blue;">`findAll()`</mark> and <mark style="color:blue;">`findOne()`</mark> methods in the <mark style="color:blue;">`UsersService`</mark> if this feature is enabled.

```typescript
omit: {
  password: true
}
```

Ideally, this should be available at the **schema** level. Let's hope for an [update](https://github.com/prisma/prisma/issues/5042) from the Prisma team. According to them, this is being worked on right now.