Annotations

Introduction
Annotation rules are implemented by feature that is in typescript called decorators and its great way how to stay inside your .ts code.
Decorator rule implementaiton is still experimental here.
Let's update our domain class user.ts and set the new label for the  name field with @Property.Label('Full Name') decorator: 
src/app/model/user.ts
1
export class User implements Entity {
2
​
3
  constructor(public uniqueName?: string,
4
  
5
              @Property.Label('Full Name')
6
              public name?: string,
7
              public description?: string, public created?: Date,
8
              public age?: number, public isAngularDeveloper: boolean = false) {
9
  }
10
​
11
  ...
12
​
Copied!
​
The .oss files have higher precedence over annotation rules, so make sure to remove label property in theUser.oss. 
src/app/rules/User.oss
1
​
2
class=User {
3
    field=uniqueName {
4
      label:"Id";
5
    }
6
    field=description {
7
      trait:longtext;
8
    }
9
    zNone => *;
10
    zLeft => uniqueName => name => description => created => age => isAngularDeveloper;
11
}
12
​
13
  class= User {
14
   operation=(edit, create) {
15
      zNone => *;
16
      zLeft => name => description;
17
   }
18
​
19
  operation=(create) {
20
      zNone => *;
21
      zLeft => name => description => created => isAngularDeveloper;
22
  }
23
}
24
​
Copied!
and run npm compile:oss
We just defined new selectors for [class=className, field=fieldName]. So in our example, this rule was created:
1
If selectors [class=User, field=name]
2
    match the current context values,
3
then apply the properties
4
    [label:"Full name"]
Copied!
We can also annotate any property like this with the general Properties decorator:
src/app/model/user.ts
1
export class User implements Entity {
2
​
3
  constructor(public uniqueName?: string,
4
  
5
              @Property.Properties('label:"Full Name"')
6
              public name?: string,
7
              public description?: string, public created?: Date,
8
              public age?: number, public isAngularDeveloper: boolean = false) {
9
  }
10
​
11
  ...
12
​
Copied!

We can similarly add trait properties like this (required):
src/app/model/user.ts
1
export class User implements Entity {
2
​
3
  constructor(public uniqueName?: string,
4
  
5
              @Property.Properties('label:"Full Name"')
6
              @Trait.Required()
7
              public name?: string,
8
              public description?: string, public created?: Date,
9
              public age?: number, public isAngularDeveloper: boolean = false) {
10
  }
11
​
12
  ...
13
​
Copied!

We can also annotate any trait property like this with the general Traits decorator:
src/app/model/user.ts
1
export class User implements Entity {
2
​
3
  constructor(public uniqueName?: string,
4
  
5
              @Property.Properties('label:"Full Name"')
6
              @Trait.Traits(['required'])
7
              public name?: string,
8
              public description?: string, public created?: Date,
9
              public age?: number, public isAngularDeveloper: boolean = false) {
10
  }
11
​
12
  ...
13
​
Copied!
The following rule is created:
1
  If selectors [class=User, field=name]
2
      match the current context values,
3
  then apply the properties
4
      [trait:required]
5
   
Copied!
Now the field name  is required and  label is set to "Full Name"
Now We've discussed how MetaIncludeComponent the ( <m-include-component> ) switches in the right component with the component property through chaining and annotation rules. As mentioned, the trait property is chained back to the context, but where are the rest of rules involved? This takes us to the MetaUI built-in rules.
Fundamentals - Previous
Chaining
Next - Fundamentals
Build-in Rules
Last modified 1yr ago
Copy link