Percentual (%) operations not saved in history
Los mantenedores suelen responder en 1 día
@Guflly ya está trabajando en esto.
Desde el 2/8/2026.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 25/100
Línea de trabajo
The payload does not name source files, so start by reproducing the steps: enter 85 × 25 % then =, and check whether the entry appears in history, comparing with a chained addition like 1 + 2 + 3. Before writing anything, review the open linked pull requests #318 and #336, since work on this bug is already under way. Done means a percentage calculation appears in history after evaluation, with no regression for the other operations.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Checklist
- I can reproduce the bug with the latest version given here.
- 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 bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.4.0
Affected Android/Custom ROM version
Agnostic, multiple
Affected device model
Agnostic, multiple
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- AC (hold down
C) 85×25%- Immediately results to 21.25 (correct)
- Check history
Feel free to do any other percentual operations other than the above.
Expected behavior
Operation shows in history.
Actual behavior
Operation missing in history (not saved).
Screenshots/Screen recordings
Trivial. No need.
Additional information
If the history was empty, then it remains empty after said operation. Thus it isn't a visual issue.
History already works outside of the evaluate button =, e.g. try doing multiple additions in succession like 1 + 2 + 3. So I suspect it's just an oversight of event attachment.
- Lenguaje dominante
- Kotlin
- Estrellas
- 450
- Forks
- 57
- Merge medio
- 2 d 30 min
- PR fusionados (30 d)
- 11
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/Calculator
-
Unit converter: Foot vs FeetAbiertofeature request needs triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
FossifyOrg/Calculator#320 ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 58/100
FossifyOrg/Calculator#338 ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
FossifyOrg/Calculator#325 ·
Los mantenedores suelen responder en 1 día
-
feature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
FossifyOrg/Calculator#313 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Rounding errorsAbiertobug needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 50/100
FossifyOrg/Calculator#308 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de FossifyOrg/Calculator
Issues similares
-
Dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
ankidroid/Anki-Android#22555 ·
Los mantenedores suelen responder en 1 día
-
Good first issue: add kotlin-spring-boot stack budget preset (Kotlin + Spring Boot 3 + Gradle)Abiertoenhancement good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
core: RAC_LLM_OPTIONS_DEFAULT.min_p disagrees with the IDL's annotated defaultPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertobug core p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
RunanywhereAI/runanywhere-sdks#1083 ·
Los mantenedores suelen responder en 5 días
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Java and Kotlin (JVM): parse gradle/wrapper/gradle-wrapper.properties with exact line locationsAbiertoarea: detector eco: java help wanted lane: free-agent roadmap size: S type: parser
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
arminazimi/evergreen#355 ·
Los mantenedores suelen responder en 1 día