简体   繁体   English

CKEditor自定义构建,包括源代码。 某些票证修复

[英]CKEditor custom build from source incl. certain ticket fix

I need to have new feature that was completed in http://dev.ckeditor.com/ticket/10931 (Allow nesting widgets) in the build. 我需要在该版本的http://dev.ckeditor.com/ticket/10931 (允许嵌套小部件)中完成新功能。

I know that it allows various ACF bugs to appear since ACF doesn't currently filter widgets within widgets, but I think we can live with it while waiting for 4.5 to arrive. 我知道它允许出现各种ACF错误,因为ACF当前不过滤小部件中的小部件,但是我认为我们可以在等待4.5到来的同时使用它。

Should it work by checking out Major branch from https://github.com/ckeditor/ckeditor-dev and doing a build on it? 是否应该通过从https://github.com/ckeditor/ckeditor-dev中检出Major分支并在其上进行构建来工作?

The branch you mentioned is unstable and not recommended for production ( see the REDAME ). 您提到的分支是不稳定的,不建议用于生产请参阅REDAME )。

This repository contains the following branches: 该存储库包含以下分支:

  • master: development of the upcoming minor release. 大师:即将发行的次要版本的开发。
  • major: development of the upcoming major release. major:即将发布的主要版本的开发。
  • stable: latest stable release tag point (non-beta). 稳定:最新的稳定版本标记点(非beta)。 *latest: latest release tag point (including betas). *最新:最新发布的标记点(包括Beta)。
  • release/ABx (eg 4.0.x, 4.1.x): release freeze, tests and tagging. release / ABx(例如4.0.x,4.1.x):释放冻结,测试和标记。 Hotfixing. 修补程序。

Even though some features have already been merged into master or major , they're not production-ready until released. 即使某些功能已经合并到mastermajor ,但在发布之前它们尚未投入生产。 This is because of unpredicted interactions between plugins and possible bugs (regressions), which are detected during comprehensive testing phase, once the code is frozen. 这是由于插件和可能的错误(回归)之间的意外交互,一旦冻结了代码,就会在综合测试阶段检测到它们。

There's always a risk that the feature is broken or the API will change, making migration to stable version of CKEditor complicated in the future. 始终存在功能中断或API更改的风险,从而使将来向CKEditor的稳定版本迁移变得复杂。 Of course, you can build CKEditor package out of unstable branch, ie with ckeditor-presets tool, but I don't recommend using it in production environment. 当然,您可以从不稳定的分支中构建CKEditor软件包,即使用ckeditor-presets工具,但是我不建议在生产环境中使用它。

Also note that building a package based on major means including other features an fixes awaiting final testing in upcoming release , which may broke your application even more. 还要注意,基于包括其他功能在内的major手段构建软件包,需要在即将发布的版本中进行最终测试的修复程序 ,可能会进一步破坏您的应用程序。 Since http://dev.ckeditor.com/ticket/10931 is quite complex, extracting related commits only may be quite tricky in your case. 由于http://dev.ckeditor.com/ticket/10931非常复杂,因此仅提取相关的提交可能会很棘手。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM