Tracebacks should include values of local variables
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2.3k
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
- possible privacy concern if URIs/bookmark/history details are included in tracebacks
- it's difficult to detect which variables this applies to from a generic `traceback()`
- difficult to display some variables
- functions (but these won't usually be relevant)
- tables need to be summarized in some fashion
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 the traceback() behavior and the privacy and display concerns listed in the issue. Determine which local values could be safely represented and how functions and tables should be handled. Done requires an agreed scope and a defined, testable traceback output, but the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100