[Editor] Overall issue for the editor

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue mentions only the early-stage Sledge editor and a future custom editor; it names no files, tests, or entry points to inspect. Start by locating the existing editor integration and defining the custom editor's scope and acceptance criteria before implementation; the issue does not currently say what done looks like.

Written by the indexing model from the issue text.

Description

The editor for the early stages will be a fork of Sledge editor. This shuold be replaced by a custom editor in the future.

Dominant language
C
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from dpeter99/ShadowEngine

All issues in dpeter99/ShadowEngine

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.