playcanvas
Migrate to playcanvas/editor Repo
Editor and Editor API code is interlinked and uses each other. As Editor front-end is now open sourced, it makes sense to migrate API into it, making it easier to make PR's as they sometimes need to change code in both places.
Looking more into code and since Editor's front-end was open sourced, I've realized that this split is pretty awful:
- Coding standards are totally different between two repos.
- The logic in editor-api repo is significantly different from editor's repo.
- A lot of code duplication between the repos.
- A lot of features you need edit in editor repo ends up in editor-api repo, so it requires joint PR's which is not easy logistically.
- Experimenting with Editor Extensions, I realized that there is pretty much always a need to touch both codebases, leading to mixed API access, between
editor.calland editor-api.
To help community to contribute more into Editor, it would be great to have editor-api "go" and end up in "editor" repo, in similar style as editor's current codebase. Especially considering that editor-api is technically not really exposed as Editor Extensions, making it's use very limited by niche devs who go Chrome Extensions route.
Yep, we'll fold it back into the Editor codebase when we get an opportunity.
