Breakpoints in console debugger for Lua
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Related dev. issue(s): https://github.com/tarantool/tarantool/issues/7456
Product: Tarantool
Since: 2.11
Root document: console debugger docs (TBD in #3195)
SME: @ tsafin @ igormunkin
Details
Please see third_party/lua/README-luadebug.md for
a description of breakpoints support introduced to the
builtin console debugger in luadebug.lua.
Requested by @tsafin in https://github.com/tarantool/tarantool/commit/cc1163a9fb08fdf9a0f84d4f052c38dcdee5bc29
Other commits that contatin the same input for documentation:
- https://github.com/tarantool/tarantool/commit/c5c2b6aa567235e1782925a51b8d2f628c9cbcbd
- https://github.com/tarantool/tarantool/commit/8a2ba4113900b3efe1230c04f941eb26d965629e
Related to the main doc issue on the console debugger #3195
Definition of done
- Breakpoints are documented in the console debugger docs
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
Read third_party/lua/README-luadebug.md and the related console debugger documentation issue #3195 first. Use the linked commits as additional documentation input, then document breakpoint support in the console debugger docs. Done means the breakpoint behavior and usage are covered there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100