[Feature Reqeuest] add extra options to CrudRequest

[Diluka]

until now. the CrudRequest has two parts. one is parsed from the client by every requests. another is options static server side config.

now there should be extra(maybe other name) the server side per request config.

it is convenient for handle different users' queries with different data scopes.

[michaelyali]

@Diluka could you please elaborate? Some examples would be awesome

[Diluka]

switch(user.role){
case 'RoleA':
 // add filters
break;
case 'RoleB':
// add other filters
break;
}

it's depend on request and parsed already has client's query filters

[Diluka]

@EnhancedCRUD(ActivityRedeemForm, {
// other configs...

// 1. HERE IS CRUD CONFIGS
  query: {
    join: {
      activity: {},
      ba: {},
    },
  },
  params: {
    activityId: {
      field: 'activityId',
      type: 'number',
    },
  },
})
export class ActivityRedeemFormController {
  @Inject() service: ActivityRedeemFormService;

  @Get('-/export.xslx')
  async exportFile(@UseCrudRequest() req: CrudRequest, @Res() res: Response, @Param('activityId') activityId: number) {
    const F = p(ActivityRedeemForm);
    delete req.parsed.page;
    delete req.parsed.limit;

   //  2. HERE MODIFIED THE CONFIGS
    req.options.query = {
      filter: [{ field: F.activityId, operator: 'eq', value: activityId }],
      join: {
        [F.ba]: {
          allow: ['nickname'],
          eager: true,
        },
      },
      sort: [{ field: F.id, order: 'ASC' }],
    };

   // do etc....
  }
}

@zMotivat0r
for example

Doing like this is WRONG

Part 2 will change Part 1. And will effect on other routes

p.s. Please ignore my encapsulations 😆