Fix test result code instead of alias printed in test certificates detail screen (EXPOSUREAPP-7781)

[jurajkusnier]

• Should work on WRU and other endpoints
• May not work on local cli

[BMItr]

@jurajkusnier
general question: why did you delete the valueSetRepo from the other viewmodel?
Wasn't it intended to be in both viewmodels?

[jurajkusnier]

@jurajkusnier
general question: why did you delete the valueSetRepo from the other viewmodel?
Wasn't it intended to be in both viewmodels?

I moved just the trigger for updating value sets, to be updated earlier (in the certificates screen). Once the values are updated they are stored in shared preferences so it's not necessary to call this trigger from the second screen.

[BMItr]

@jurajkusnier
general question: why did you delete the valueSetRepo from the other viewmodel?
Wasn't it intended to be in both viewmodels?

I moved just the trigger for updating value sets, to be updated earlier (in the certificates screen). Once the values are updated they are stored in shared preferences so it's not necessary to call this trigger from the second screen.

Yes I got it.
Could you please check whether the Viewmodel is called BEFORE the testCertificat && BEFORE the Vaccination Part?
If its not the case we will move the bug around.

[jurajkusnier]

@jurajkusnier
general question: why did you delete the valueSetRepo from the other viewmodel?
Wasn't it intended to be in both viewmodels?

I moved just the trigger for updating value sets, to be updated earlier (in the certificates screen). Once the values are updated they are stored in shared preferences so it's not necessary to call this trigger from the second screen.

Yes I got it.
Could you please check whether the Viewmodel is called BEFORE the testCertificat && BEFORE the Vaccination Part?
If its not the case we will move the bug around.

Yes, as we moved Vaccinations to the Certificates tab, I don't see any way how to access Vaccinations without opening the Certificates tab at least once.

[jurajkusnier]

@jurajkusnier
general question: why did you delete the valueSetRepo from the other viewmodel?
Wasn't it intended to be in both viewmodels?

I moved just the trigger for updating value sets, to be updated earlier (in the certificates screen). Once the values are updated they are stored in shared preferences so it's not necessary to call this trigger from the second screen.

Yes I got it.
Could you please check whether the Viewmodel is called BEFORE the testCertificat && BEFORE the Vaccination Part?
If its not the case we will move the bug around.

Yes, as we moved Vaccinations to the Certificates tab, I don't see any way how to access Vaccinations without opening the Certificates tab at least once.

I reverted changes in VaccinationListViewModel after discussion regarding concerns for potential future changes in screen flow

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication