API - r.connect
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
We should write an example on how to catch errors and how to access the error types (in all languages)
It's somehow the documentation for https://github.com/rethinkdb/rethinkdb/issues/1926
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 reading the requested r.connect documentation context and the linked RethinkDB issue 1926. Add examples showing how to catch errors and access error types for all supported languages; done means each language has clear, working documentation for both tasks.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100