Editor for different project types
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 59
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 26
Description
Reusable components:
- Code editor, #2803
- History
- Load/export & persistence solution
Routing / page structure note:
- Supporting multiple project types may mean providing dedicated editor pages per type (not necessarily a single unified editor page that switches by type).
- Route-level work (how editor entry URLs map to a specific type/editor implementation) should be captured here, while project detail/community route-level work lives in #2805/#2807.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the reusable components listed here, especially the code editor in #2803, then compare the route-level scope with #2805 and #2807. Define how editor entry URLs map to each supported project type and whether dedicated editor pages are needed. Done means the project-type editor structure and routing approach are implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100