playcanvas / playcanvas/editor

Link projects to share common assets and scripts

Open
#340 9 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🔥🔥‎ area: templates enhancement
Dominant language
TypeScript
Stars
1.3k
Forks
215
Avg merge
1d 29m
Merged PRs (30d)
30

Description

The copy/paste feature is a god sent! Thank you all who made it happen :)

With the new feature in place, a new behavior patterns emerged. One such is to develop a common framework or an SDK, that holds scripts with convenience methods and a template scene layout with screens and all. When a new project starts, we copy/paste a framework to the new project, so there is a boilerplate, and as we develop the project, we add to the original boilerplate additional common methods.

When a new project starts, we grab the framework from the latest project, since it has new methods and stuff, remove the pieces not needed and use it in the new project. The cycle goes on.

This creates diffferent versions of potentially the same framework. It would be super nice, if there was an option to link a project. Like you link libraries and projects in Microsoft Visual Studio. This would allow to always point to the latest version of the framework which would be maintained in its own project.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the editor's project and asset-management entry points and any existing library-linking behavior. Done would mean a project can reference a separate framework project so its shared scripts and scene assets stay available from the latest version.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.