NativeScript / NativeScript/ios-device-lib
Why are we using binary output for nodejs communication under Windows?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16
- Forks
- 8
- Avg merge
- 19h 29m
- Merged PRs (30d)
- 2
Description
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 inspecting IOSDeviceLib/IOSDeviceLib.cpp around line 1298 and trace the Windows nodejs communication path that produces the binary output. Determine whether the behavior is intentional or incorrect; done means the rationale or required change is established and reflected in the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100