ngx-hierarchy-chart
v0.0.21
Published
The `ngx-hierarchy-chart` creates hierarchical chart.
Downloads
46
Maintainers
Readme
ngx-hierarchy-chart
The ngx-hierarchy-chart
creates hierarchical chart.
Table of Contents
Installation
You can install the packages using following command.
$ npm install d3
$ npm install ngx-hierarchy-chart
Usage
|Property|Type|Default|Description
|---|---|---|---|
|name|string
|xxx
| Name of the node
|children|object {}
|xxx
| Children of the nodes
|height|number
| Default - 700
|Height of the chart
|width|number
| Default - 500
|Width of the chart
|data|Node {}
| |The array of child nodes
app.module.ts
import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import { NgxHierarchyChartModule } from 'ngx-hierarchy-chart';
import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
@NgModule({
declarations: [
AppComponent
],
imports: [
CommonModule,
AppRoutingModule,
NgxHierarchyChartModule
],
providers: [],
bootstrap: [AppComponent]
})
export class AppModule { }
app.component.html
<ngx-hierarchy-chart [chartdata]="nodes"> </ngx-hierarchy-chart>
style.scss
.node text {
font: 12px sans-serif;
}
.node--internal text {
text-shadow: 0 1px 0 #fff, 0 -1px 0 #fff, 1px 0 0 #fff, -1px 0 0 #fff;
}
.link {
fill: none;
stroke: #9E9E9E;
stroke-width: 2px;
}
.node circle {
fill: #1784a2;
stroke-width: 2px;
}
app.component.ts
import { Component } from '@angular/core';
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.scss']
})
export class AppComponent {
nodes: any = {data:{
"name": "A1",
"children": [
{
"name": "B1",
"children": [
{
"name": "C1"
},
{
"name": "C2"
},
{
"name": "C3"
},
{
"name": "C4"
},
{
"name": "C5"
},
{
"name": "C6"
}
]
},
{
"name": "B2",
"children": [
{
"name": "C1"
},
{
"name": "C2"
},
{
"name": "C3",
"children":[
{
"name": "D1"
},
{
"name": "D2"
}
]
}
]
}
]
},
width:800,
height:600
};
}
Inputs
|Name|Type|Description
|---|---|---|
|chartdata
|Node
object|The Node
object that contains node info mentioned above
Steps
This library was generated with Angular CLI version 9.1.12.
Code scaffolding
Run ng generate component component-name --project ngx-hierarchy-chart
to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project ngx-hierarchy-chart
.
Note: Don't forget to add
--project ngx-hierarchy-chart
or else it will be added to the default project in yourangular.json
file.
Build
Run ng build ngx-hierarchy-chart
to build the project. The build artifacts will be stored in the dist/
directory.
Publishing
After building your library with ng build ngx-hierarchy-chart
, go to the dist folder cd dist/ngx-hierarchy-chart
and run npm publish
.
Running unit tests
Run ng test ngx-hierarchy-chart
to execute the unit tests via Karma.
Further help
To get more help on the Angular CLI use ng help
or go check out the Angular CLI README.
Publishing library to public npm repository:
To publish the library to the public npm repository, you have to sign up for an account with npmjs. You can create your npmjs account here: https://www.npmjs.com/signup
Now run the below command from the terminal and provide your npm credentials when asked:
npm adduser
(Note: This is a one-time operation only and you can skip this step if you have already logged in.)
Anytime, you can also verify that you are logged in or not by using the following command:
npm whoami
Once logged in, you need to navigate up to your library directory from the dist directory. In short,
Finally, we are ready to publish our library. Remember that, we already used npm pack so we can just publish our .tgz file (Otherwise you need to run the npm pack command first)
npm publish - -access public
Then we can see the published package on npm at this URL:
https://www.npmjs.com/package/< library- name>
Now that we have created and published this library we can use it anywhere in any project by running the following command:
npm install — save <library-name>@0.0.1
(here 0.0.1 is the version number of a library, which is necessary)
Few Adjustments: As a good programming practice, we should provide some unique name for the library.
Because our npm’s public registry will sure have many packages with these similar names. So you can follow the approach to add your npm’s username with your library name so that it can be uniquely identified and also to avoid the errors while you publish it.
For this, you can change the name parameter of the package.json file of your library project. (from projects folder)
Here this name is having npm-username/library-name
value.
And now you can follow the publishing steps described above.
I hope you find this article useful. Thanks for reading!