Documentation Request: Testing Example
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 117
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 44
Description
Hey There!
Love working with this library, and the documentation is super comprehensive, appreciate it!
I wonder if you'd be able to provide documentation that includes examples on how to test both the TS and native side of nitro-modules. As far as I've seen this is the only piece thats missing, and it would be great to have this story covered.
Thanks in advance!
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
No files, tests, or entry points are named. Start by reviewing the existing documentation and testing setup for TypeScript and native Nitro modules; the work is done when both sides have clear testing examples documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, kotlin, swift, typescript
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100