npm package: @ngx-form/material
Description: Angular Material components to set html dynamic elements configuration of `@ngx-form/element package`
Author: Ścibor Rudnicki
Latest version: 1.0.3-beta.1

<img src="http://ngx-form.wwwdev.io/color_logo_transparent_background.png" alt="ngx-form logo" title="ngx-form" align="right" width="128" />

# @ngx-form/material

[![Build Status](https://travis-ci.org/ngx-form/material.svg)](https://travis-ci.org/ngx-form/material)
[![Semver](http://img.shields.io/SemVer/2.0.0.png)](http://semver.org/spec/v2.0.0.html)
[![npm version](https://badge.fury.io/js/%40ngx-form%2Fmaterial.svg)](https://badge.fury.io/js/%40ngx-form%2Fmaterial)
[![GitHub version](https://badge.fury.io/gh/ngx-form%2Fmaterial.svg)](https://badge.fury.io/gh/ngx-form%2Fmaterial)

[![Known Vulnerabilities](https://snyk.io/test/npm/@ngx-form/material/badge.svg)](https://snyk.io/test/npm/@ngx-form/material)
[![GitHub issues](https://img.shields.io/github/issues/ngx-form/material.svg)](https://github.com/ngx-form/material/issues)
[![GitHub forks](https://img.shields.io/github/forks/ngx-form/material.svg)](https://github.com/ngx-form/material/network)
[![GitHub stars](https://img.shields.io/github/stars/ngx-form/material.svg)](https://github.com/ngx-form/material/stargazers)
[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/ngx-form/material/master/LICENSE)

Angular Material components to set html dynamic elements configuration of `@ngx-form/element` package.

** **Work in progress** **


## Table of contents
* [Demo](#demo)
* [Installation](#installation)
* [Usage](#usage)
* [Versioning](#versioning)
* [Git commit](#git-commit)
* [License](#license)
* [Donate](#donate)


## Demo

Usage demonstration of a @ngx-form/material package coming soon

## Installation

To install, run:

```bash
npm install --save 
  @angular/material@2.0.0-beta.10
  @ngx-form/material 
  @ngx-form/interface@0.7.0 
  @ngx-form/element@2.0.13
```

## Usage
```typescript
```

## 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-form

## Donate
[Click to donate](https://donorbox.org/help-creating-open-source-software)