Development under this git repository is discontinued and future improvements will continue under io.hyperify.core.
Join our Discord to discuss about our software!
Our enterprise library for TypeScript.
We don't have traditional releases. This project evolves directly to our git repository in an agile manner.
This git repository contains only the source code for a compile time use case. It is meant to be used as a git submodule in a NodeJS or webpack project.
See also hg.fi for easy NPM package creators for your project and other additional modules from us.
Copyright (c) Heusala Group. All rights reserved. Licensed under the MIT License (the "License");
Run the installation commands from your project's root directory. Usually it's where your package.json is located.
For these sample commands we expect your source files to be located in ./src and we'll use ./src/fi/hg/core for location for our submodule.
Setup git submodule:
mkdir -p src/fi/hg
git submodule add git@github.com:heusalagroup/fi.hg.core.git src/fi/hg/core
git config -f .gitmodules submodule.src/fi/hg/core.branch mainNext install our required dependencies (newest lodash library and reflect-metadata library):
npm install --save-dev lodash @types/lodash
npm install --save-dev reflect-metadataWe also use the moment library for time:
npm i 'moment-timezone' '@types/moment-timezone'If you're going to develop NodeJS app, you might want to install also types for NodeJS (this should be obvious though):
npm install --save-dev @types/nodeThe "experimentalDecorators": true, option must also be enabled in your
TypeScript configuration in your project's ./tsconfig.json.
Git doesn't automatically clone your sub modules.
You'll need to command:
git clone --recurse-submodules git@github.com:heusalagroup/your-project.git your-project...or:
git clone git@github.com:heusalagroup/your-project.git your-project
cd your-project
git submodule init
git submodule updateLater when you want to update your submodules, you may do:
git pull
git submodule update --remoteNPM doesn't provide a good way to implement pure compile time typescript libraries.
We would have to compile our whole library in our bundle even though you probably don't use everything.
It wouldn't be possible to use compile time optimizations and other ENV based feature flags.
Our simple wrapper for console which allows naming the log context.
import LogService from "./src/fi/hg/core/LogService";
const LOG = LogService.createLogger("FooService");
export class FooService {
run(arg: string) {
LOG.debug("Did something: ", arg);
}
}This is a simple observer implementation for implementing synchronous in-process events for a local service.
You'll use it like this:
import Observer from "./src/fi/hg/core/Observer";
enum FooEvent {
CHANGED = "FooService:changed",
}
class FooService {
private static _data: any;
private static _data : any;
private static _observer : Observer<FooEvent> = new Observer<FooEvent>("GeoIpService");
public static getData () : any {
return this._data;
}
public static on (name : FooEvent, callback : ObserverCallback<FooEvent>) : ObserverDestructor {
return this._observer.listenEvent(name, callback);
}
public static refreshData() {
HttpService.doSomething()
.then((response) => {
this._data = response.data;
this._observer.triggerEvent(FooEvent.CHANGED);
})
.catch((err) => {
console.error("Error: ", err);
});
}
}
FooService.on(FooEvent.CHANGED, () => {
const currentData = FooService.getData();
// ...
});
FooService.refreshData();HTTP request mapping annotations for TypeScript in the same style as in Java's Spring @RequestMapping.
import Request, {
GetMapping,
PostMapping,
RequestBody,
ResponseEntity,
RequestHeader,
RequestParam,
Headers
} from "./src/fi/hg/core/Request";
export interface ListDTO<T> {
pageNumber: number;
pageSize: number;
content: Array<T>;
}
@RequestMapping("/foo/users")
@RequestMapping("/users")
export class UserController {
private readonly _userService: UserService;
constructor(userService: UserService) {
this._userService = userService;
}
@GetMapping("/", "/list")
public async getUserList(
@RequestParam("p", Request.ParamType.INTEGER)
pageNumber: number = 0,
@RequestParam("l", Request.ParamType.INTEGER)
pageSize: number = 10,
@RequestHeader('accept', {defaultValue: '*/*'})
accept: string
): Promise<ResponseEntity<ListDTO<UserModel>>> {
// const parsedPageNumber = pageNumber ? parseInt(pageNumber, 10) : 0;
// const parsedPageSize = pageSize ? parseInt(pageSize, 10) : 10;
return ResponseEntity.ok({
pageNumber: pageNumber,
pageSize: pageSize,
content: await this._userService.getUserList(pageNumber, pageSize),
});
}
@GetMapping("/items/{id}")
public async getUserList(
@PathVariable('id')
id: string
): Promise<ResponseEntity<Json>> {
return ResponseEntity.ok({
itemId: id
});
}
@PostMapping("/addUser")
public async addUser (
@RequestBody user : Json,
@RequestHeader headers : Headers
) : Promise<ResponseEntity<Json>> {
const host = headers.getHost();
await this._userService.addUser(user);
return ResponseEntity.ok({
user: user,
host: host
});
}
}You can also use:
@Request.mappinginstead of@RequestMapping,@Request.paraminstead of@RequestParam,@Request.headerinstead of@RequestHeader,@Request.bodyinstead of@RequestBody,@Request.getMapping(...)instead ofGetMapping(...)orRequest.mapping(Request.Method.GET, ...)@Request.putMapping(...)instead ofPutMapping(...)orRequest.mapping(Request.Method.PUT, ...)@Request.postMapping(...)instead ofPostMapping(...)orRequest.mapping(Request.Method.POST, ...)@Request.deleteMapping(...)instead ofDeleteMapping(...)orRequest.mapping(Request.Method.DELETE, ...)
For the actual server implementing REST API, see next chapter.
This project also includes a simple and pure NodeJS implementation for the REST server implementing our Request annotated controllers:
import RequestServer from "./fi/hg/core/RequestServer";
const server = new RequestServer("http://0.0.0.0:3000");
server.attachController(UserController);
server.start();See also our ProcessUtils for best practices implementing complete runtime support.
We also provide a Spring Data inspired annotation mechanism for entities and CrudRepository implementation.
It's available from @heusalagroup/fi.hg.repository.
This utility class includes a simple implementation for runtime .env file support.
import ProcessUtils from "./fi/hg/core/ProcessUtils";
// Must be first import to define environment variables before anything else
ProcessUtils.initEnvFromDefaultFiles();This utility function can be used to implement default shutdown handlers for the common runtime events.
It will hook into events exit, SIGTERM, SIGINT, SIGUSR1, SIGUSR2 and uncaughtException.
The shutdownHandler will be called only once.
If an exception is thrown, the errorHandler will be called with the exception.
import ProcessUtils from "./fi/hg/core/ProcessUtils";
const server = new Server();
server.start();
ProcessUtils.setupDestroyHandler( () => {
server.stop();
}, (err : any) => {
LOG.error('Error while shutting down the service: ', err);
});This project was originally under Sendanor's organization in Github.
If that's the case for your local submodule, fix your git's remote:
git remote set-url origin git@github.com:heusalagroup/fi.hg.core.git