A collection of utilities for Baloise web applications.

• Utils
• Pipes
• Validators

• Packages
• Contributing

Library	Status	Description
@baloise/web-app-utils		A collection of JavaScript utilities like simple functions, models and integration logic.
@baloise/web-app-pipes		A collection of pipe function to transform raw values in a certain format.
@baloise/web-app-pipes-angular		Proxy package for angular applications.
@baloise/web-app-pipes-vue		Proxy package for vue applications.
@baloise/web-app-validators		A collection of validator functions.
@baloise/web-app-validators-angular		Proxy package for angular applications.
@baloise/web-app-validators-vue		Proxy package for vue applications.

We gratefully accept contributions to the Baloise Web App Utilites, but expect new feature requests and changes to be approved by the Baloise Web Community before creating a pull request.

Baloise Web App Utilities is free to use for anybody building a Baloise product or website, and the Baloise community is always working to make it better. Contributors like you help to make Baloise Web App Utilities great, and so we’re glad you’re here.

Contributions are not limited to code. We also encourage feedback, documentation, new designs, and tools.

All you need is a public GitHub account to get started. Most contributions begin with a GitHub issue using one of these templates:

• Ask a question
• Report a bug
• Request a feature

Users are members of the community who use Baloise Web App Utilities guidelines, assets, and tooling. Anyone can be a user, and we encourage users to participate in the community as much as possible.

Contributors are members of the community who contribute to Baloise Web App Utilities in a material way. Anyone can be a contributor. In addition to participating as a user, you can also contribute by:

• Reporting bugs or missing features through GitHub issues
• Fixing bugs, adding features, and improving documentation

Maintainers are members of the community who are committed to the success of individual Baloise Web App Utilities projects. In addition to their participation as a contributor, maintainers:

• Label, close, and manage GitHub issues
• Close and merge GitHub pull requests

The Baloise Web App Utilities typically use a fork and pull request workflow for contributions

Baloise Web App Utils are divided into multiple NPM packages. Development for all of the packages happens inside one mono repository. Follow the below steps to get the dev environment up and running.

To work with this project a recent LTS version of NodeJS and npm is required. Make sure you've installed and/or updated Node before continuing.

To start building a new utilities, clone this repo to a new directory:

git clone https://github.com/baloise/web-app-utils.git web-app-utils
cd web-app-utils

• Run npm install in the root directory to install all dependencies of the packages
• Run npm run build in the root directory to build all packages
• Run npm run test in the root directory to run all tests of packages
• Run npm run docs in the root directory to generate the api documentation of the utilities

All our validators are located in the packages/utils dir.

Navigate into the component package:

cd packages/utils

To run the test use this command:

npm run test

The structure of the utils in the folder utils is importend, because out of it the documentation is automatically generate as well as the adapter for our supported frameworks like angular.

The comment block has a short description and an example part for the documentaion.

Each utility function needs to be exported.

/**
 * Returns `true` if the arrays are equal
 *
 * ```typescript
 * isValidMonetaryNumber(`1'000.99`) // true
 * ```
 */
export function isValidMonetaryNumber(stringValue: string): boolean {
  // utility logic
  return any
}

All our validators are located in the packages/validators dir.

Navigate into the component package:

cd packages/validators

Each validator has its own test file.

To run the test use this command:

npm run test

The structure of the validator is importend, because out of it the documentation is automatically generate as well as the adapter for our supported frameworks like angular.

The comment block has a short description and an example part for the documentaion.

The first function receivs the options parameter and the second function gets the value to validate.

import { BalValidatorFn } from './validator.type'

/**
 * Returns `true` if the value date is before the given date
 *
 * ```typescript
 * BalValidators.isCustom((value) => value > 2)(3) // true
 * ```
 */
export function isCustom(validatorFn: BalValidatorFn): BalValidatorFn {
  return function (value: any) {
    return validatorFn(value)
  }
}

All our pipe functions are located in the packages/pipes dir.

Navigate into the component package:

cd packages/pipes

Each pipe has its own test file.

To run the test use this command:

npm run test

The structure of the pipe function is importend, because out of it the documentation is automatically generate as well as the adapter for our supported frameworks like angular.

The comment block has a short description and an example part for the documentaion.

The pipe are simple functions which always return a string.

import { isEmpty } from '@baloise/web-app-utils'
import capitalize from 'lodash.capitalize'

/**
 * Transforms the given string parameter to capitalize string.
 *
 * ```typescript
 * balCapitalize('baloise') // Baloise
 * ```
 */
export function balCapitalize(value: string | null | undefined): string {
  if (isEmpty(value)) {
    return ''
  } else {
    return capitalize(value as string)
  }
}

It is important to follow the conventional commits rules of the sematic versioning.

Note that the lerna release uses the commit messages to determine the type of changes in the codebase. The changelog gets generated out of the commit messages.

1. Create a new git branch.
2. Create a pull request and follow the conventional commits rules.
3. After merging the github action .github/release.yml will release the changes immediately.
   • First it determines the new version out of the git commit messages
   • Then it releases is on npm
   • The changelog is generated out of the git commit messages aswell.

We are following the Karam Git Message guideliness.

Here are some examples of the release type that will be done based on a commit messages: