NativeScript / NativeScript/ios-device-lib
What is the expected way to debug the native library?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16
- Forks
- 8
- Avg merge
- 19h 29m
- Merged PRs (30d)
- 2
Description
As the native library is usually spawned by a nodejs code located outside of this repository - what is the expected way to debug the calls to the spawned process?
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 tracing how the native library is spawned by the external nodejs code and identify the available process-debugging entry points. Document the expected way to debug calls to the spawned process, including the steps needed to reproduce that workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nodejs
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100