Tips for merging DTO (Data Transfer Object) with non-DTO objects

Question

Tips for merging DTO (Data Transfer Object) with non-DTO objects

I'm currently working on a new endpoint and I need to validate only two parameters (limit and offset) with the dto. The third parameter is not supposed to be checked.

My controller test code is not functioning as expected. When I try to use it, the endpoint returns an error message saying: "property startDate should not exist". How can I fix this issue and achieve the desired result? Are there any other alternatives I should consider in this scenario (besides creating a new dto)?

@Get()
methodName(
  @Query('startDate') startDate: Date,
  @Query() paginationDto: PaginationDto
) {
  return this.reviewsService.methodName(startDate, paginationDto);
}

typescript nestjs

Answer 1

Answer №1

Instead of generating a new data transfer object

Your top choice would be to use with strict validation from the ValidationPipe (meaning not permitting unknown properties to the DTO). This is because @Query() represents req.query and @Query('startDate') stands for req.query['startDate']. Unless you create custom decorators that extract the values from the original location, like @PullFromQuery('startDate') which both grabs the data and alters the req.query, similar to this:

export const PullFromQuery = createParamDecorator((data: string, ctx: ExecutionContext) => {
  const req = ctx.switchToHttp().getRequest();
  if (data) {
    const retData = req.query[data];
    delete req.query[data];
    return retData;
  }
  return req.query;
})

However, I suggest refraining from modifying the req.query unless absolutely necessary and just go ahead with creating the second DTO.

Answer 2

Instead of generating a new data transfer object

Your top choice would be to use with strict validation from the ValidationPipe (meaning not permitting unknown properties to the DTO). This is because @Query() represents req.query and @Query('startDate') stands for req.query['startDate']. Unless you create custom decorators that extract the values from the original location, like @PullFromQuery('startDate') which both grabs the data and alters the req.query, similar to this:

export const PullFromQuery = createParamDecorator((data: string, ctx: ExecutionContext) => {
  const req = ctx.switchToHttp().getRequest();
  if (data) {
    const retData = req.query[data];
    delete req.query[data];
    return retData;
  }
  return req.query;
})

However, I suggest refraining from modifying the req.query unless absolutely necessary and just go ahead with creating the second DTO.

Tips for merging DTO (Data Transfer Object) with non-DTO objects

Answer №1

Similar questions

How can I access other properties of the createMuiTheme function within the theme.ts file in Material UI?

Why did the homepage load faster than the app.component.ts file?

Unlocking the potential of deeply nested child objects

Utilizing the array.map method to access the key of an object within an array of arrays in TypeScript

I am puzzled as to why I keep receiving the error message "Cannot read property 'poPanel' of undefined"

React Native is throwing an error message saying that the Component cannot be used as a JSX component. It mentions that the Type '{}' is not assignable to type 'ReactNode'

Issue with bundling project arises post upgrading node version from v6.10 to v10.x

Transferring AgGrid context in a functional React component

What is the best way to refresh a Component upon sending data to the server?

Preventing click propagation for custom react components nested within a MapContainer

Using Angular Form Builder to assign a value depending on the selected option in a dropdown menu

Display the modal in Angular 8 only after receiving the response from submitting the form

Can I assign a value from the tagModel to ngx-chips in an Angular project?

The MemoizedSelector cannot be assigned to a parameter of type 'string'

Invalid component prop provided to ButtonBase in Material UI. Ensure that the children prop is correctly rendered in this custom component

Node C++ Addon Typescript declaration file

Describing a property of an interface as the determined form of a conditional type that is generic

Compiling with tsc --build compared to tsc --project

Issues with my transpiled and typed TypeScript npm module: How can I effectively use it in a TypeScript project?

Using Angular2's NgFor Directive in Components