8 comments (8 comments)0 reactions (0 reactions)0 assignees (0 assignees)Java17,072 stars (17,072 stars)3,750 forks (3,750 forks)batch import
enhancementhelp wanted
Description
tag need support. v21 and AppCompat already support v9 and up api level.
Contributor guide
- Tech stack
- javaandroid
- Domain
- mobile
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- half day
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Knowledge of Android VectorDrawableFamiliarity with Fresco's image pipeline
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- Investigate how Fresco currently handles Drawable resources, specifically the DraweeController and PipelineDraweeController. Look at existing support for other drawable types. The issue mentions v21 and AppCompat already support VectorDrawable for API 9+, so research how to integrate that into Fresco's resource loading. Check if there are any related PRs or comments in the issue that hint at the approach. The implementation likely requires adding a method to convert vector drawable resources to Android Drawable objects within Fresco's drawable hierarchy.