@casus-campus/cc-support v0.11.1

CcSupport

This project was generated with Angular CLI version 7.2.0 supported the instructions of this article.

Provided components and services

• cc-dynamic-content-viewer (component): Renders hyperlinks in html content as dialog, tooltip, external link or collapsible.

Requirements

• @angular/material
• hammerjs

Installation

1. Install npm install --save @casus-campus/cc-support

2. Add to app.module.ts

  imports: [
    \\ ...
    CcSupportModule,
  ]

3. Apply material theme

@use '@casus-campus/cc-support' as *;

@include cc-support-theme($theme);

Development

This repository contains two projects: the CC-Support library (@casus-campus/cc-support) and a test application (lib-tester). To see changes of the library files (projects/casus-campus/cc-support/src/lib) inside the test app (projects/lib-tester/src/app), you need to build the library with npm run build.

Development server

Run ng serve for a dev server for the lib-tester. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Build

Run npm run build to build the library. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

Publish library to NPM

Publishing the library is only needed, if the develop branch has some changes that are not already in the production branch. The latest production commit reflects the latest published version on NPM.

Semi-automated (preferred)

• make sure that develop branch is checked out (git checkout develop)
• make sure that the tests succeed (ng test @casus-campus/cc-support)
• increase version in ./projects/casus-campus/cc-support/package.json (following SemVer)
• commit and push changes
• merge into production (git checkout production && git merge develop)
• push changes (git push)

Manual

• make sure that develop branch is checked out (git checkout develop)
• make sure that the tests succeed (ng test @casus-campus/cc-support)
• increase version in ./projects/casus-campus/cc-support/package.json (following SemVer)
• commit changes
• merge into production (git checkout production && git merge develop)
• perform npm run pack
• perform npm publish ./dist/casus-campus/cc-support/[tgz-file] (make sure to be login first via npm login)
• push changes (git push) and tag (git push --tag origin production)