Не описаны опции для net.box call и eval
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Нет описания всех опций для net.box call и eval
https://www.tarantool.io/en/doc/latest/reference/reference_lua/net_box/#lua-function.conn.call
Related dev. issue(s): GitHub link(s)
Product: Tarantool, Cartridge, TDG, connectors, tools?
Since: product version
Audience/target: who will read it and for what task?
Root document: where to add or update documentation
SME: @ expert to ask for more information
Details
- What should we write about?
- What's most important?
- Examples of code and configuration.
- Related development issues and/or commits.
Definition of done
- do A
- do B
Planning checklist
- Pick product label:
- Pick type label:
- reference,
- getting started,
- user_guide, etc.
- Estimate complexity in storypoints in the title
- Add to Documentation board → Backlog
Note: issue templates are in beta. Give your feedback in #1869.
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 with the linked net.box conn.call reference and locate the corresponding documentation for net.box eval. Compare both sections to determine which options are undocumented, then update the relevant reference content with the missing descriptions and examples. The issue's definition of done is still placeholder text, so confirm the expected scope with a documentation maintainer before starting.
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
- Needs clarification
- Newbie friendliness
- 25/100