Component: Debugging
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.2k
- Forks
- 115
- Avg merge
- 17h 28m
- Merged PRs (30d)
- 50
Description
Dark doesn't have a great debugging experience right now.
We have no support for breakpoints and step-debugging, and runtime errors are often opaque.
Dark-classic had some almost-excellent debuggability through the use of our Traces, but those aren't yet accessible in dark-next.
Once the baseline editing experience has advanced a bit, we need to circle back here, starting with how Traces fit into the debugging experience.
- review old #3778
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 reviewing old issue #3778 and the existing Dark-classic Traces experience described here. The work is complete when a concrete debugging baseline is defined for dark-next, including how Traces fit into that experience; no implementation files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100