Jasonette / Jasonette/JASONETTE-iOS
Turn components into CocoaPods module
Open
Nobody has claimed this yet.
code
enhancement
- Dominant language
- JavaScript
- Stars
- 5.2k
- Forks
- 347
- PR merge metrics
- No merged PRs in 30d
Description
We've successfully separated out action extensions to CocoaPods module. I think we can go even further and apply the similar principle to UI components. Need to think of how to handle decoupling, etc.
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 identified. Start by reviewing how the action extensions were separated into a CocoaPods module, then map the UI components and their dependencies before deciding how decoupling should work; done means the UI components are provided as a CocoaPods module without unwanted coupling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100