Porting guide should document transpiled porting
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
https://skip.tools/docs/porting/
As discussed here https://github.com/orgs/skiptools/discussions/382 this porting guide is entirely about porting via Skip's native/bridged mode.
The existing documentation should be updated to make it clear that it's talking entirely about --native modules.
There should also be a guide on how best to port modules in transpiled mode.
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 porting guide at https://skip.tools/docs/porting/ and read discussion #382 for the distinction between native/bridged and transpiled modes. Update the guide to identify its --native scope, then add guidance for porting modules in transpiled mode; done means both workflows are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- documentation, mobile-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100