feat: add core

# EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs

# editorconfig.org

root = true

[*]

indent_style = space

indent_size = 2

# We recommend you to keep these unchanged

end_of_line = lf

charset = utf-8

trim_trailing_whitespace = true

insert_final_newline = true

[*.md]

trim_trailing_whitespace = false

 No newline at end of file

# Logs

logs

*.log

npm-debug.log*

yarn-debug.log*

yarn-error.log*

# Runtime data

pids

*.pid

*.seed

*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover

lib-cov

# Coverage directory used by tools like istanbul

coverage

# nyc test coverage

.nyc_output

# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)

.grunt

# Bower dependency directory (https://bower.io/)

bower_components

# node-waf configuration

.lock-wscript

# Compiled binary addons (http://nodejs.org/api/addons.html)

build/Release

# Dependency directories

node_modules/

jspm_packages/

# Typescript v1 declaration files

typings/

# Optional npm cache directory

.npm

# Optional eslint cache

.eslintcache

# Optional REPL history

.node_repl_history

# Output of 'npm pack'

*.tgz

# Yarn Integrity file

.yarn-integrity

# dotenv environment variables file

.env

# ignore ide files

.idea

.vscode

# ignore lib

lib

# ignore docs

docs

image: node:lts-alpine

cache:

  key: ${CI_COMMIT_REF_SLUG}

  paths:

    - lib

    - node_modules

before_script:

  - npm install

stages:

  - build

  - test

  - deploy

build:

  stage: build

  script:

    - npm run build

audit:

  stage: test

  script:

    - npm audit

test:

  dependencies:

    - build:build

  stage: test

  script:

    - npm test

pages:

  stage: deploy

  script:

    - npm run documentation

    - mv docs public

  only:

    - /^v[0-9]+\.[0-9]+\.[0-9]+$/

  artifacts:

    paths:

      - public

## What's wrong with the current model?

???

## How should the model be instead?

???

## Why should the model be that way?

??? - Describe use case!

/label ~bug ~meeting

## What needs to be remodelled?

??? - Describe use case!

## How is the current model not sufficient?

???

## Which changes are necessary?

???

## Do the proposed changes impact current use cases?

???

/label ~feature ~meeting