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

Fix Locations not showing on register. #3457

Merged
merged 6 commits into from
Aug 23, 2024
Merged

Conversation

Lentumunai-Mark
Copy link
Contributor

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

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

Signed-off-by: Lentumunai-Mark <lentumunai.mark@students.jkuat.ac.ke>
@Lentumunai-Mark
Copy link
Contributor Author

This PR entails

Fixing the issue of locations not showing on the register

Copy link

codecov bot commented Aug 22, 2024

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 27.3%. Comparing base (115c4f4) to head (dba3bb4).
Report is 2 commits behind head on main.

Files Patch % Lines
...register/fhircore/quest/ui/main/AppMainActivity.kt 0.0% 2 Missing ⚠️
...t/ui/multiselect/MultiSelectBottomSheetFragment.kt 0.0% 2 Missing ⚠️
...er/fhircore/engine/data/local/DefaultRepository.kt 0.0% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##              main   #3457   +/-   ##
=======================================
  Coverage     27.2%   27.3%           
- Complexity     742     746    +4     
=======================================
  Files          276     276           
  Lines        13811   13823   +12     
  Branches      2504    2504           
=======================================
+ Hits          3764    3777   +13     
+ Misses        9540    9527   -13     
- Partials       507     519   +12     
Flag Coverage Δ
engine 64.3% <0.0%> (-0.4%) ⬇️
geowidget 11.4% <ø> (ø)
quest 5.5% <0.0%> (+<0.1%) ⬆️

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

Files Coverage Δ
...egister/fhircore/quest/ui/main/AppMainViewModel.kt 3.8% <ø> (ø)
...er/fhircore/engine/data/local/DefaultRepository.kt 65.0% <0.0%> (ø)
...register/fhircore/quest/ui/main/AppMainActivity.kt 0.0% <0.0%> (ø)
...t/ui/multiselect/MultiSelectBottomSheetFragment.kt 0.0% <0.0%> (ø)

... and 3 files with indirect coverage changes

Signed-off-by: Lentumunai-Mark <lentumunai.mark@students.jkuat.ac.ke>
Signed-off-by: Lentumunai-Mark <lentumunai.mark@students.jkuat.ac.ke>
Signed-off-by: Lentumunai-Mark <lentumunai.mark@students.jkuat.ac.ke>
@ellykits ellykits merged commit b55d720 into main Aug 23, 2024
4 of 5 checks passed
@ellykits ellykits deleted the Fix-include-flattened-locations branch August 23, 2024 07:56
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.

2 participants