@frui.ts/generator
v1.0.0-rc.4
Published
Frui.ts code generator
Downloads
367
Keywords
Readme
Frui.ts code generator
Provides code generation for:
Inversify configuration
Generates files needed for InversifyJS DI container:
- A 'decorators' file with
@injectable
and@inject
decorators so that you don't need to write them in your code. - A 'registry' file with
container.bind()
statements.
Following service export scenarios are supported:
- No constructor
- Custom constructor with parameters
- Static factory method
Dependency injection scenarios supported:
- Constructor parameters:
- instance (
constructor(dependecy: SomeService)
) - custom static factory method (
constructor(dependecyFactory: ReturnType<typeof SomeService.Factory>)
) - automatic factory method (
constructor(dependecyFactory: () => SomeService)
)
- instance (
Usage
Usage: fruits-generate inversify [options]
Generate Inversify configuration files
Options:
-p, --project <fileName> TS project file (default: "./tsconfig.json")
-c, --config <fileName> Custom configuration file
--no-decorators Do not generate decorators file
--decorators-output <relativePath> Decorators output file path (default: "src/di.decorators.ts")
--no-registry Do not generate registry file
--registry-output <relativePath> Registry output file path (default: "src/di.registry.ts")
-h, --help display help for command
Custom configuration is expected to be a JSON file with the following structure:
export interface IConfig {
factoryName: string;
rules: {
pattern: string;
addDecorators?: boolean;
registerAutoFactory?: boolean;
scope: "none" | "singleton" | "transient";
identifier?: "$class" | "$interface" | string;
}[];
}
Use none
life scope if you don't want the service registered but still want the decorators generated. This is useful if you want to register the service yourself.
Identifier
determines what service identifier shall be used when registering the service:
$class
- the class constructor will be used (default)$interface
- name of the first interface that the service implements will be used- any other key - the key will be used as a string
Default configuration file:
{
"factoryName": "Factory",
"rules": [
{
"pattern": "Service$",
"identifier": "$class",
"addDecorators": true,
"registerAutoFactory": false,
"scope": "singleton"
},
{
"pattern": "ViewModel$",
"identifier": "$class",
"addDecorators": true,
"registerAutoFactory": false,
"scope": "transient"
},
{
"pattern": "Repository$",
"identifier": "$class",
"addDecorators": true,
"registerAutoFactory": false,
"scope": "transient"
}
]
}
Example
With these classes:
export default class AService {}
import { interfaces } from "inversify";
export default class BService {
// serviceA shall be injected from DI
// someParam must be provided when instantiating
constructor(private serviceA: AService, someParam: any) {}
static Factory({ container }: interfaces.Context) {
return (someParam: any) => new BService(container.get(AService), someParam);
}
}
export default class CService {
constructor(serviceBFactory: ReturnType<typeof BService.Factory>) {
const serviceB = serviceBFactory("someParam");
}
}
The following files will be generated:
// di.decorators.ts
import { decorate, inject, injectable } from "inversify";
decorate(injectable(), AService);
decorate(injectable(), BService);
decorate(injectable(), CService);
decorate(inject(BService.Factory) as any, CService, 0);
// di.registry.ts
import { Container, interfaces } from "inversify";
export default function registerServices(container: Container) {
container.bind<AService>(AService).toSelf().inSingletonScope();
container.bind<interfaces.Factory<BService>>(BService.Factory).toFactory(BService.Factory);
container.bind<CService>(CService).toSelf().inSingletonScope();
}
Views registration
Generates a file referencing all Frui.ts views that call registerView()
from the @frui.ts/views
package. Therefore you just need to import this single generated file, and all your views will be registered.
Usage
Usage: fruits-generate views [options]
Generate view registrations
Options:
-p, --project <fileName> TS project file (default: "./tsconfig.json")
-o, --output <relativePath> Output file path (default: "src/views/index.ts")
-h, --help display help for command
OpenApi entities
Generates typescript entities defined in the referenced OpenAPI definition. The entities also contain validation rules as defined in the OpenAPI definition and static function for conversion from JSON format (e.g., string->Date).
Note that if the file already exists during generation, only the class' body is regenerated. For example, you can remove the export default
part or add custom code to the file.
Usage
Usage: fruits-generate openapi|swagger [options]
Generate OpenAPI client files
Options:
-p, --project <fileName> TS project file (default: "./tsconfig.json")
-c, --config <fileName> Custom configuration file
-o, --output <relativePath> Output folder path (default: "src/entities")
--no-validation Do not generate validation rules
--no-conversion Do not generate conversion function
-h, --help display help for command
Custom configuration is expected to be a JSON file with the following structure:
export interface IConfig {
api: string;
observable?: ObservableConfig;
enums?: "enum" | "string";
dates?: "native" | "date-fns";
validations?: Record<string, ValidationConfig>;
}
// helper types
interface HasExclude {
exclude?: string[];
}
export type ObservableConfig =
| boolean
| {
entities: Record<string, boolean | HasExclude>;
properties?: HasExclude;
};
export type ValidationConfig =
| string // generated rule name
| boolean // 'false' disables rule generation
| {
name?: string; // generated rule name
filter?: string; // regex string matched against the rule param
};
Default configuration file:
{
"api": "https://fruits-demo.herokuapp.com/api/swagger-json",
"observable": {
"entities": {
"EnumValue": false,
"User": {
"exclude": ["code"]
},
"Partner": {
"include": ["name"]
}
},
"properties": {
"exclude": ["id", "created"]
}
},
"enums": "enum",
"dates": "native"
}
Validations
You can control what validation rules are generated and how. The validations
property of the configuration is a key-value with the following meaning:
- key - name of the validation rule. Available rules are defined in the
Restrictions
enum - value - configuration of the following type:
- object - detailed configuration:
- name - name of the resulting validation rule (by default is the same as the key/restriction name)
- filter - validation rule will be generated only if its param matches this regex string
- string - name of the resulting validation rule. Shortcut for
{ name: 'foo' }
- boolean - if set to
false
, the rule will not be generated.
- object - detailed configuration:
Example
{
"api": "openapi/swagger.yml",
"observable": {
"entities": {
"EnumValue": false,
"User": {
"exclude": ["code"]
},
"Partner": {
"include": ["name"]
}
},
"properties": {
"exclude": ["id", "createdAt"]
}
},
"enums": "enum",
"dates": "date-fns",
"validations": {
"number": "isNumber",
"readOnly": false,
"nullable": {
"filter": "false"
},
}
}
Generated file
export default class User {
id!: number;
@observable
email!: string;
@Transform(value => (value ? new Date(value) : undefined), { toClassOnly: true })
@Transform(value => (value ? formatISO(value, { representation: "date" }) : undefined), { toPlainOnly: true })
createdAt!: Date;
@observable
@Transform(value => (value ? new Date(value) : undefined), { toClassOnly: true })
@Transform(value => (value ? formatISO(value, { representation: "date" }) : undefined), { toPlainOnly: true })
updatedAt!: Date;
@observable
role!: number;
static ValidationRules = {
id: { required: true, isNumber: true },
email: { required: true, format: "email" },
createdAt: { required: true },
updatedAt: { required: true },
role: { required: true, isNumber: true },
};
}