# Angular Integration

This feature is provided through the ckeditor4-angular npm package.

CKEditor 4 offers a native Angular integration through the CKEditor 4 Angular component. It provides deep integration of CKEditor 4 and Angular that lets you use the native features of the WYSIWYG editor inside an Angular component. The CKEditor 4 Angular component is compatible with Angular versions 2.0 and later.

## # Basic Usage

In order to create an editor instance in Angular, install the ckeditor4-angular npm package as a dependency of your project:

npm install --save ckeditor4-angular


After installing, import CKEditorModule to your application:

import { CKEditorModule } from 'ckeditor4-angular';

@NgModule( {
imports: [
...
CKEditorModule,
...
],
…
} )


You can now use the <ckeditor> tag in the component template to include the rich text editor:

<ckeditor data="<p>Hello, world!</p>"></ckeditor>


The data attribute used in the example above is responsible for setting the editor’s data.

## # Customizing CKEditor Preset or Version

By default, the CKEditor 4 Angular component loads the Standard-All preset of the latest CKEditor 4 release from the CDN when creating the first editor. This behavior can be altered by setting the value of the editorUrl attribute in the template to point to the desired CKEditor location:

<ckeditor editorUrl="https://your-website.example/ckeditor/ckeditor.js"></ckeditor>


Note that this attribute must be assigned before the first component is initialized.

<script src="my-custom-build/ckeditor.js"></script>
<script src="your-app-bundle.js"></script>


## # Choosing the Editor Type

By default, the CKEditor 4 Angular component creates an inline editor with a fixed UI. This editor type will be referred to as a divarea editor. To create an editor with a floating UI, add the type property with a value of inline:

<ckeditor
data="<p>Some initial data</p>"
type="inline"
></ckeditor>


Every other value of the type property will be treated as a divarea.

Notes:

## # Integration with ngModel

The component implements the ControlValueAccessor interface and works with ngModel.

To use it, first create a model in your component:

@Component( {
...
} )
export class MyComponent {
public model = {
editorData: '<p>Hello, world!</p>'
};
...
}


Then you can use the model in the template to enable the two-way binding.

<ckeditor [(ngModel)]="model.editorData"></ckeditor>


## # Supported @Input properties

The following @Input properties are supported by the CKEditor 4 Angular component:

### #editorUrl

The URL address to ckeditor.js. Refer to Customising CKEditor Preset or Version for more information.

### #config

Custom configuration can be passed to the editor with the config attribute passed to <ckeditor> in the component template. The following example shows how to change the toolbar configuration:

<ckeditor
data="<p>Editor' content</p>"
[config]="{ toolbar: [ [ 'Bold' ] ] }"
></ckeditor>


All configuration options can be changed this way.

### #data

The initial data of the WYSIWYG editor. It can be a static value:

<ckeditor data="<p>Hello, world!</p>"></ckeditor>


or a shared parent component’s property:

@Component( {
...
} )
export class MyComponent {
public editorData = '<p>Hello, world!</p>';
}

<ckeditor [data]="editorData"></ckeditor>


### #tagName

Specifies the tag name of the HTML element on which the WYSIWYG editor will be created.

The default tag is <textarea>.

<ckeditor tagName="textarea"></ckeditor>


### #readOnly

The editor can be set to read-only mode with the readOnly property:

<ckeditor
data="<p>Editor's content</p>"
></ckeditor>


This property takes precedence over the config.readOnly setting.

## # Supported @Output properties

The following @Output properties are supported by the CKEditor 4 Angular component:

### #ready

Fires when the editor is ready. It corresponds with the editor#instanceReady event.

### #change

Fires when the content of the editor has changed. It corresponds with the editor#change event. For performance reasons this event may be called even when data has not really changed.

<ckeditor (change)="onChange(\$event)"></ckeditor>


import { CKEditor4 } from 'ckeditor4-angular/ckeditor';

@Component( {
...
} )
export class MyComponent {
public onChange( event: CKEditor4.EventInfo ) {
console.log( event.editor.getData() );
}
...
}


### #dataChange

Fires when the content of the editor has changed. In contrast to change, it only emits when the data really changed thus can be successfully used with [data] and the two-way [(data)] binding.

### #focus

Fires when the editor’s editable is focused. It corresponds with the editor#focus event.

### #blur

Fires when the editing view of the editor is blurred. It corresponds with the editor#blur event.

### # Note

Callbacks bound to each of the events are called with eventInfo. For importing and usage of the EventInfo interface see the change example.

## # Editor Instance

In most cases there is no need to break the encapsulation provided by the CKEditor 4 Angular component as the WYSIWYG editor configuration and event handlers are configurable via the component’s properties. However, if you need access to the editor object, you can use the instance property of the component’s instance:

component.instance.getData();


Please note that this property is initialised asynchronously, when the component is ready.

## # Types

CKEditor types can be installed from @types/ckeditor. Note that they are not maintained by the CKEditor team, so we cannot guarantee that they are up to date.