wordpress-mobile / wordpress-mobile/WordPress-iOS
Optimization: reduce asset catalog size in extensions
Open
Nobody has claimed this yet.
[Type] Task
General
- Dominant language
- Swift
- Stars
- 3.9k
- Forks
- 1.2k
- Avg merge
- 23h 51m
- Merged PRs (30d)
- 58
Description
The app extensions include the same asset catalogs that the app does, which has the following negative effects:
- The catalog gets compiled multiple times. There is an opportunity to reduce the build time by 10 seconds.
- The catalog is included in every extension, significantly increasing their size.
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
The issue identifies duplicated asset catalogs in the app extensions but names no files or tests. Start by inspecting the Xcode project and extension asset-catalog build membership, then compare the resulting extension sizes and build times. Done means extensions no longer compile or include the app's catalogs without losing required assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- build-system, mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100