-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration to TS #367
Migration to TS #367
Conversation
…ix." This reverts commit ea77c72.
…alization, in case the handler after initialization
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I am not in the process, I do not understand why we have two samples:
sample/
demo-*/
I can guess that the first is just a sample using the component and some CKEditor 5 build, while the second is a demo application (more realistic scenario). It would be good to describe both in README and explain which should be checked before releasing a new version. Maybe we do not need the sample/
directory anymore. Instead, we should develop example applications that could be checked using E2E tests on CI.
WDYT about dropping support for non-supported React versions? It means the CKEditor component will require React 18.0+. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Suggested merge commit message (convention)
Feature: Migrate package to TypeScript. Closes ckeditor/ckeditor5#13542.
MAJOR BREAKING CHANGE: Integration now requires Editor version 37 or later.