* implemented dao, entitiy, database, module - wip

* Added cross ref classes for joining data

* Adjusted daos

* - Added ContactDiaryModule to AppComponent - Reduced code a bit

* missing interface change

* Uniform naming

* Defined methods for contact diary repo

* added mapper extension

* fixed naming, Implement contact diary repo

* Added repo to module, Flows shall return lists

* Added foreign key constraints - outdated

* Clear contact diary database on DataReset, removed unneccessary element

* removed singletons

* adjustments to new tech spec

* Adjusted daos from stash

* Added new daos to related classes

* Redefined contact diary repo

* Implemented contact diary repo

* Added mission dao annotations

* sorting opportunity

* sourcecheck clean

* cleanUp, added db schema, removed old stuff

* missing call

* ForeigenKey must be in entity declaration

* Added contact diary db test, removed broken tests

* added autogenerate primarykey

* Moved data joining from App-Lvl to database

* Explicit naming in entities

* sourcecheck & ktlint clean

Co-authored-by: BMItter <berndus@gmx.de>

* Submission upload, first draft.
Storing Symptoms and TEKs.

TODO:
* Change upload task to use stored data.
* Blocking upload task
* Tests

* Update symptoms on each screen.
Integrate permission request and automatic TEK history update.

TODO:
* Cancel dialog
* Blocking upload task
* Tests

* Add submission on cancel behavior.

* LINTs and unit tests.

* Hooking up navigation and first break through on TAN based submission.

* Hook up navigation for QR Code to test result without consent.

* Fix positive result consent given submission: Abort to Main Screen

* Restore default environment.

* Adjust notification target fragment.

* Address LINTs

* Clean up symptoms introduction nav actions.

* Fix tests

* Your test result available screen

* Formatting

* Lint fix

* Initial refactoring on the Submission flow.
Trimming down SubmissionViewModel.kt

* Refactored submission tan, and began instrumentation tests. Intro, Dispatcher and Tan complete

* Adapted instrumentation tests after merge - added ToDos

* Completed boilerplate submission instrumentation tests. Verification and screenshots to follow

* Fix lints

* More lint issues.

* Fix instrumentation test dependency missmatch.

* Move screenshot related permissions into a debug AndroidManifest.xml,
such that they don't get included in production builds.

* Added missing new line to manifest

Co-authored-by: Oliver Zimmerman <oezimmerman@gmail.com>
Co-authored-by: Kolya Opahle <k.opahle@sap.com>
Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* Introduced `TracingCardState` and `TracingDetailsState`.
Removed all direct viewmodel/livedata access from all nested layouts for `TracingViewModel`.
Removed `FormatterRiskHelper`.
Introduced logic to reactively update the UI state if bluetooth, location or tracing state changes.

TODO:
* Finish tests in TracingCardStateTest.kt and TracingDetailsStateTest.kt
* Finish TracingDetailsViewModel.kt and TracingCardViewModel.kt
* Remove obsolete dependencies on TracingViewModel.kt and singletons RiskLevelRepository.kt, TracingRepository.kt

* Breakthrough, cards update again.

* Further cleanup of TracingViewModel.kt, TracingRepository.kt
Still not quite there yet, too many calls going into every direction, back and forth, instead of just top->down, but we are getting there.
We want data flow from business logic code to the UI, keep the UI KISS.

* Update TracingCardState tests to account for changes

* More refactoring, TracingViewModel.kt is now finally gone.

* Fix risk details card, we reuse the cardviewmodel but need to overwrite the `showDetails` flag depending from where it's used.

* Refactored several properties (notification related) out of SettingsViewModel/Repository

* Fix injection

* Refactoring submission related databinding code on the home fragment

* Make TracingRepository.kt injectable and change viewmodel scoping for refresh calls to app scope.

* Remove additional formatter calls from submission cards on home screen.

* Refactored additional SubmissionViewModel logic into SubmissionRepository on the Homescreen.
First UI Test is now passing.

Simplified ViewModel instantiation related code.
Prepared HomeFragment for smoother UI state changes, less reloading.

* Improved home,tracing-details and tracing-settings loading behavior, less flickering.
Fixed LiveData value assignment on background-thread.

* New reactive provider for Bluetooth and Location status.
Cleaned up ConnectivityHelper.kt partially.

* Implement remaining tests, batch 1.

* Implement remaining tests, batch 2.

* Fix lint issues.

* Removed a few codesmells and code duplication.
Introduced Flow.shareLatest(...)

* Removed unused parameters.

* LINT fixes.

* Fix unit test failing due to missing mocks.

* Address PR comments.

* Improve UI loading states, remove flickering.

* Remove log spam due to polling values, add extra abort condition that checks for cancellation.

Co-authored-by: ralfgehrer <mail@ralfgehrer.com>

* Added MVVM and DI to OnboardingFragment

* Refactored OnboardingFragment to work with MVVM and DI

* Refactored OnboardingPrivacyFragment to work with MVVM and DI

* Moved navigation functions from OnboardingTracingFragment to VM

* Refactored OnboardingTestFragment to work with MVVM and DI

* Refactored OnboardingNotificationsFragment to work with MVVM and DI

* Added ktlintFormat changes

* Added intstrumentation tests skeleton for each fragment in Onboarding flow

* Removed unused import

* Changed Onboarding fragment top constraint

* Removed unnecessary VM declaration from layouts

* Added requested changes

* Added new lineat end of files

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>
Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>
Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

Introduce VM injection for home screen and enable screen testing (EXPOSUREAPP-2946, EXPOSUREAPP-2948) (#1320)

* Rename "MainFragment" to "HomeFragment"
Add VM injection.
Move initial logic into VM.

TODO: Move more code, write more tests.

* Additional refactoring, moving logic out of the Fragment.
Moving code into their own encapsulated routines/components.
Use composition to reuse TracingViewModel, SettingsViewModel and SubmissionViewModel

* Introduce @AppContext annotation to prevent anyone mistaking it for something else.

* Add VM to RiskDetailsFragment

* Simplify nested viewmodels, here: TracingViewModel.kt

* Add skeletons instrumentation test skeleton for single fragments with injection and mocking.

* Address PR comments.

* Introduce sealed events class, + some refactoring.

* Make the linter happy.