playcanvas / playcanvas/editor
Add per-asset import options
Open
Nobody has claimed this yet.
area: asset import
enhancement
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 215
- Avg merge
- 1d 29m
- Merged PRs (30d)
- 30
Description
It would be useful to have persistent per-asset import options.
For example see #120. Ideally when dragging in the asset for the first time, the user is able to specify whether the asset is treated as a binary blob or converted into a project asset type.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #120 and tracing the existing flow for dragging an asset into the editor. Identify where the initial import choice is handled and how asset settings persist. Done means a first-time import can choose binary blob or project asset type, and that choice is retained per asset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100