Extract icon from folder if it's the only one present in it
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
The payload names no files, so begin by locating the folder code in the Kotlin Android launcher and checking how a folder's item count is handled when an app is removed. Reproduce by putting two apps in a folder, removing one, and confirming the folder stays a folder. Done means a folder left with one app is shown as that app's normal icon, and the change is covered by a test or a manual check described in the PR.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
I'd like for a single icon in a folder to automatically turn into a normal icon.
Why do you want this feature?
It's a minor UX improvement: since a folder is a way to group multiple apps in a tile, it doesn't really make sense to have a folder with a single icon in it.
Also good first issue for those who are interested.
Additional information
Flow:
- I have two app icons in a folder
- I remove one of them
- The folder with the single icon in it automatically turns back into the normal icon
- Lenguaje dominante
- Kotlin
- Estrellas
- 703
- Forks
- 85
- Merge medio
- 1 d 20 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Launcher
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
FossifyOrg/Launcher#453 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
FossifyOrg/Launcher#447 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
FossifyOrg/Launcher#446 ·
Los mantenedores suelen responder en 1 día
-
Lock dispositionAbiertofeature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
FossifyOrg/Launcher#469 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
FossifyOrg/Launcher#465 ·
Los mantenedores suelen responder en 1 día
Todos los issues de FossifyOrg/Launcher
Issues similares
-
design good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
scribe-org/Scribe-Android#739 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
xybrid-ai/xybrid#661 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
android bug kotlin vulkan
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
maplibre/maplibre-native-ffi#852 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día