Document "Code" usage
Open
Nobody has claimed this yet.
add details
cartridge
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Haven't found docs on how to use "Code" tab in webui:
- what's under this tab
- what it is capable of
- possible use cases
- step by step guide on how to write code
- possible drawbacks (e.g. live code is not versioned in git)
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
Use the webui's Code tab and the attached screenshot as the starting point. Document what the tab contains, its capabilities and use cases, provide a step-by-step guide to writing code, and explain drawbacks such as live code not being versioned in git. Done means these requested topics are covered in the Tarantool documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100