After some testing it looks like hosting local files by karma is a no-go for us thus it will require setting up files dependencies in a correct order which may break in the future. The best option seems to enable development testing with build CKEditor by using local CKEditor endpoint instead of CDN. However, configuring Angular requires a bit of hacking around because of the missing option to use system environmental variables nor CLI specific options https://github.com/angular/angular-cli/issues/4318.
TBO I really miss some way to easily pass custom CKEditor URL. It's pretty simple with karma.conf.js because this file is processed by Node, so it's possible to execute process.env.CKEDITOR_URL to get URL from system variables e.g. CKEDITOR_URL=http://localhost:1040/apps/ckeditor/ckeditor.js ng test but it's not possible within samples and e2e tests, so I think that consistency is preferred here.
After some testing it looks like hosting local files by karma is a no-go for us thus it will require setting up files dependencies in a correct order which may break in the future. The best option seems to enable development testing with build CKEditor by using local CKEditor endpoint instead of CDN. However, configuring Angular requires a bit of hacking around because of the missing option to use system environmental variables nor CLI specific options https://github.com/angular/angular-cli/issues/4318.
TBO I really miss some way to easily pass custom CKEditor URL. It's pretty simple with
karma.conf.jsbecause this file is processed by Node, so it's possible to executeprocess.env.CKEDITOR_URLto get URL from system variables e.g.CKEDITOR_URL=http://localhost:1040/apps/ckeditor/ckeditor.js ng testbut it's not possible within samples and e2e tests, so I think that consistency is preferred here.Closes #8