Scenarios that includes viewmodels.

[remult]

Scenarios that includes viewmodels.

[noam-honig]

First of all, thanks :)

With regards to ViewModels, there are several available strategies that you can employ.

• To control the hiding and exposing of properties, you can use the inclideInApi option of a field, for example:

class User{
...
@Fields.string({ includeInApi:false })
password='';
}

Or an authorization rule:

class User{
...
@Fields.string({ includeInApi:"Admin" })
password='';
}

Or even a condition that is based on the instance itself:

class User{
...
@Fields.string<User>({ includeInApi:(remult)=>/* some rule */  })
password='';
}

• You can use the serverExpression field option, to enrich the view model with server data. Here's an example from the CRM-Demo

• You can also use the sqlExpression if you're using Postgres to create more sophisticated sql's

• You can use multiple entities that view the same database table and optionally use inheritance to reduce duplicity, for example:

@Entity("deliveries")
export class Deliveries {
    @Fields.uuid()
    id?: string;
    @Fields.string()
    name = '';
    @Fields.boolean()
    deleted = false;
}

@Entity<ActiveDeliveries>("activeDeliveries", {
    dbName: 'deliveries',
    backendPrefilter: {
        deleted: false
    }
})
export class ActiveDeliveries extends Deliveries {
}

• For the more complex scenarios, you can use the Backend Methods

If you have a specific example that you are interested in, please share it here, and we'll be happy to review it together.

[3ldar]

Thanks for the reply. I have been mentoring a group for a while and we have been reviewing some nodejs frameworks these questions came to mind while in that brief review.