https://github.com/ngx-core/common
Some Angular 2+ features used in other ngx libraries
https://github.com/ngx-core/common
angular angular2 component dynamic dynamically ngx-core
Last synced: 2 months ago
JSON representation
Some Angular 2+ features used in other ngx libraries
- Host: GitHub
- URL: https://github.com/ngx-core/common
- Owner: ngx-core
- License: mit
- Created: 2017-04-26T11:50:39.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2017-07-19T11:29:37.000Z (almost 8 years ago)
- Last Synced: 2025-01-17T11:15:35.351Z (4 months ago)
- Topics: angular, angular2, component, dynamic, dynamically, ngx-core
- Language: TypeScript
- Homepage:
- Size: 57.6 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# @ngx-core/common
Some Angular 2+ features used in other ngx libraries
## Table of contents
* [Installation](#installation)
* [Usage](#usage)
* [Versioning](#versioning)
* [Git commit](#git-commit)
* [License](#license)
* [Donate](#donate)
## Installation
To install, run:
```bash
npm install @ngx-core/common --save
```
## Usage
* [DynamicComponentClass](https://github.com/ngx-core/common/wiki/DynamicComponentClass)
* [Type component](https://github.com/ngx-core/common/wiki/Type-component)
## Versioning
Semantic Versioning 2.0.0 http://semver.org/
**Given a version number MAJOR.MINOR.PATCH, increment the:**
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
**FAQ**
How should I deal with revisions in the 0.y.z initial development phase?
>The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.
How do I know when to release 1.0.0?
>If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.
## GIT commit
- AngularJS Git Commit Message Conventions https://gist.github.com/stephenparish/9941e89d80e2bc58a153
- http://karma-runner.github.io/0.10/dev/git-commit-msg.html
## License
MIT © ngx-core
## Donate
[Click to donate](https://donorbox.org/help-creating-open-source-software)