fields

  userSchema = {
   firstName,
   lastName,
   workspaceId: <-- eagerly loaded to worspace
  }
  
  applyAccessFilters()
  regular -> 'find.books' -> you should only 'workspace.name'
  
  fields = '// workspace.name' //'workspace'
  
  RULE:
  I should be able to limit first level and eager/second level fields that are visible
  
  BLACKLIST APPROACH: where you forcefully deny fields
  ex: regular findOne.users -> blacklist: ['worskape.id', 'workspace.secretKey', ...];
  WHITELIST APPROACH: where you allow a limited set of fields
  ex: regular findOne.users -> whitelist: ['worskape.name'];
  
  BOTH APPROACHES CAN WORK AT THE SAME TIME:
  1. you have a blacklist
   - deny those fields
  2. you have a whitelist
   - you will allow only those fields
  3. you have both a blacklist and a whitelist
   - whitelist is dominant
   
  
  find({ query, offset, limit, fields }) {
    // this.eagerMap = ['workspace'];
    // we have to type of fields to limit: first level fields and eagerly loaded fields
    // fields needs to reflect both
    const fields =  ['firstName','lastName', 'workspaceId', 'workspace', 'workspace.name'];
    const firstLevelFields = fields.filter(f => !this.eagerMap.find(f));
    const secondLevelFields = fields.filter(f => this.eagerMap.find(f));
    
    if (firstLevelFields.length) {
     // limit query result fields to this list
    }
    
    return new GenericQuery(query).toKnex(
      this.ormModel
        .query()
        .eager(secondLevelFields)
        .skipUndefined()
        .offset(offset)
        .limit(limit)
    );
  }