-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #4135, Fix part of #5070: In FractionInteraction UI, leave submit button enabled when answer is empty. #5224
Fix #4135, Fix part of #5070: In FractionInteraction UI, leave submit button enabled when answer is empty. #5224
Conversation
… empty. Show an error on submitting an empty answer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had some questions: Please see inline.
utility/src/main/java/org/oppia/android/util/math/FractionParser.kt
Outdated
Show resolved
Hide resolved
app/src/test/java/org/oppia/android/app/parser/FractionParsingUiErrorTest.kt
Outdated
Show resolved
Hide resolved
...c/main/java/org/oppia/android/app/player/state/itemviewmodel/FractionInteractionViewModel.kt
Show resolved
Hide resolved
Hi @masclot, it looks like some changes were requested on this pull request by @adhiamboperes. PTAL. Thanks! |
This PR should be complete now. |
@adhiamboperes PTAL. Should I also include @BenHenning as reviewer? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @masclot, this LGTM.
@BenHenning, I am happy with this solution, but could you take a high level pass to verify the approach?
Hi @masclot, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @masclot! This looks really good. Just had a few comments--PTAL.
...c/main/java/org/oppia/android/app/player/state/itemviewmodel/FractionInteractionViewModel.kt
Outdated
Show resolved
Hide resolved
...c/main/java/org/oppia/android/app/player/state/itemviewmodel/FractionInteractionViewModel.kt
Outdated
Show resolved
Hide resolved
...c/main/java/org/oppia/android/app/player/state/itemviewmodel/FractionInteractionViewModel.kt
Outdated
Show resolved
Hide resolved
...java/org/oppia/android/app/player/state/itemviewmodel/MathExpressionInteractionsViewModel.kt
Show resolved
Hide resolved
utility/src/main/java/org/oppia/android/util/math/FractionParser.kt
Outdated
Show resolved
Hide resolved
@BenHenning PTAL |
Hi @masclot, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue. |
Hi @masclot, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @masclot! Really sorry for the delayed review. This LGTM.
...java/org/oppia/android/app/player/state/itemviewmodel/MathExpressionInteractionsViewModel.kt
Show resolved
Hide resolved
<!-- READ ME FIRST: Please fill in the explanation section below and check off every point from the Essential Checklist! --> ## Explanation <!-- - Explain what your PR does. If this PR fixes an existing bug, please include - "Fixes #bugnum:" in the explanation so that GitHub can auto-close the issue - when this PR is merged. --> Fix #4135: The only thing left is removing the TODO comment, as the tests were created in #5224 ## Essential Checklist <!-- Please tick the relevant boxes by putting an "x" in them. --> - [x] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".) - [x] Any changes to [scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets) files have their rationale included in the PR explanation. - [x] The PR follows the [style guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide). - [x] The PR does not contain any unnecessary code changes from Android Studio ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)). - [x] The PR is made from a branch that's **not** called "develop" and is up-to-date with "develop". - [x] The PR is **assigned** to the appropriate reviewers ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)). ## For UI-specific PRs only <!-- Delete these section if this PR does not include UI-related changes. --> If your PR includes UI-related changes, then: - Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes - For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see [RTL guide](https://github.com/oppia/oppia-android/wiki/RTL-Guidelines)) - Add a video showing the full UX flow with a screen reader enabled (see [accessibility guide](https://github.com/oppia/oppia-android/wiki/Accessibility-A11y-Guide)) - For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included - Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing Co-authored-by: Adhiambo Peres <59600948+adhiamboperes@users.noreply.github.com>
Fix part of #5070: In FractionInteraction UI, leave submit button enabled when answer is empty. Show an error on submitting an empty answer. The error message already exists and is the same as in oppia/oppia#18379.
Demo video: leave_submit_button_enabled_on_empty_answer_v3.webm
The new error messages for empty inputs on submit are listed here: oppia/design-team#71(comment)
I added an accessibility-label exemption for FractionInputInteractionViewTestActivity as this activity is only used in tests.
Fix #4135: incidentaly, this change also fixes #4135, since I had to split the tests for FractionInputInteraction
Essential Checklist
For UI-specific PRs only
If your PR includes UI-related changes, then: