Skip to content
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

Add Exit Dialog #3487

Merged
merged 17 commits into from
Oct 7, 2024
Merged

Add Exit Dialog #3487

merged 17 commits into from
Oct 7, 2024

Conversation

hamza-vd
Copy link
Contributor

@hamza-vd hamza-vd commented Sep 11, 2024

IMPORTANT: Where possible all PRs must be linked to a Github issue

Fixes #3479

Engineer Checklist

  • I have written Unit tests for any new feature(s) and edge cases for bug fixes
  • I have added any strings visible on UI components to the strings.xml file
  • I have updated the CHANGELOG.md file for any notable changes to the codebase
  • I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
  • I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
  • I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

  • I have verified Unit tests have been written for any new feature(s) and edge cases
  • I have verified any strings visible on UI components are in the strings.xml file
  • I have verifed the CHANGELOG.md file has any notable changes to the codebase
  • I have verified the solution has been implemented in a configurable and generic way for reuseable components
  • I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

@hamza-vd hamza-vd changed the title Add exit dialog Add Exit Dialog Sep 11, 2024
@hamza-vd hamza-vd marked this pull request as draft September 11, 2024 12:22
@hamza-vd hamza-vd assigned hamza-vd and unassigned hamza-vd Sep 11, 2024
Copy link

codecov bot commented Sep 11, 2024

Codecov Report

Attention: Patch coverage is 6.66667% with 14 lines in your changes missing coverage. Please review.

Project coverage is 27.2%. Comparing base (8cf03cf) to head (c04f509).

Files with missing lines Patch % Lines
...register/fhircore/quest/ui/main/AppMainActivity.kt 6.6% 14 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##              main   #3487     +/-   ##
=========================================
- Coverage     27.2%   27.2%   -0.1%     
  Complexity     756     756             
=========================================
  Files          278     278             
  Lines        14219   14234     +15     
  Branches      2581    2582      +1     
=========================================
+ Hits          3880    3881      +1     
- Misses        9801    9815     +14     
  Partials       538     538             
Flag Coverage Δ
engine 63.8% <ø> (ø)
geowidget 15.4% <ø> (ø)
quest 5.6% <6.6%> (+<0.1%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...register/fhircore/quest/ui/main/AppMainActivity.kt 5.1% <6.6%> (+0.1%) ⬆️

@hamza-vd
Copy link
Contributor Author

Dialog content

@hamza-vd hamza-vd marked this pull request as ready for review September 16, 2024 06:34
Comment on lines 315 to 318
if (
navController.currentDestination?.id?.equals(R.id.geoWidgetLauncherFragment)!! ||
navController.currentDestination?.id?.equals(R.id.registerFragment)!!
) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand this implementation is based on the assumption that the entry point to the app can either be the map or register. However, a user can redirect to a register screen from the profile using the onSubmitQuestionnaire actions. Would it be possible to check if there is no more entry in the navController back stack instead to prompt this dialog?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Condition updated

Copy link
Collaborator

@ellykits ellykits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, see my comment.

@ellykits ellykits merged commit e9bc0de into main Oct 7, 2024
4 of 5 checks passed
@ellykits ellykits deleted the issue-3479 branch October 7, 2024 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Override onBackPressed() and prompt user before exiting from App
4 participants