Expose ckConfig interface

[piernik]

We can provide ckconfig in config attribute.
Can You export it's complete interface in @ckeditor/ckeditor5-angular ?
It woulde be very nice to have full type support.

[pomek]

I guess the EditorConfig interface describes the configuration enough.

I can imagine that your idea has some sense but it will be hard to maintain. EditorConfig contains options for most of the CKEditor 5's plugins.

If we create a new plugin, it will force release this repository because the new plugin may introduce the new option in the interface.

[piernik]

You're right. So maybe only present keys that has any as value?

[pomek]

cc: @ma2ciek

[ma2ciek]

This is a complicated thing. As I've described in ckeditor/ckeditor5#504 (comment), each plugin should extend some base CKEditor5 interfaces and then our editor builds should concatenate these type declarations into one file, so they can be published with these declarations easily.

I've provided simple declarations in the https://github.com/ckeditor/ckeditor5-angular/blob/master/src/ckeditor/ckeditor.ts, but obviously, they're incomplete. You can look at https://github.com/ckeditor/ckeditor5-angular/blob/master/src/app/simple-usage/simple-usage.component.ts to see, how they're used. Those can be imported as import { CKEditor5 } from '@ckeditor/ckeditor5-angular/ckeditor'; I'll try to change the path in the future, so the import { CKEditor5 } from '@ckeditor/ckeditor5-angular'; will be also possible.

[ma2ciek]

I'm closing it since it's already solved (https://github.com/ckeditor/ckeditor5-angular/blob/master/src/ckeditor/ckeditor.ts#L15).