Always use the handleEvent(s) function the same way.

[bmarty]

Just a small cleanup on our codebase.

[github-actions]

📱 Scan the QR code below to install the build (arm64 only) for this PR.

If you can't scan the QR code you can install the build via this link: https://i.diawi.com/bGCKwT

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.73%. Comparing base (f1389cb) to head (fdd4e21).
⚠️ Report is 16 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #5672   +/-   ##
========================================
  Coverage    79.73%   79.73%           
========================================
  Files         2420     2420           
  Lines        65029    65029           
  Branches      8296     8296           
========================================
  Hits         51848    51848           
  Misses       10209    10209           
  Partials      2972     2972           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jmartinesp]

This has the side effect of not displaying the actual error when something unexpected happens in the tests related to the state values, instead displaying an error saying it can't print the actual error because it doesn't know how to debug-print the state value because it doesn't have the kotlin reflection library.

We could maybe add kotlin-reflect as a testImplementation dependency, see if that fixes the issue.

[bmarty]

This has the side effect of not displaying the actual error when something unexpected happens in the tests related to the state values, instead displaying an error saying it can't print the actual error because it doesn't know how to debug-print the state value because it doesn't have the kotlin reflection library.

When we have such issue in the test, we now know that it's because there are unconsumed state(s) (some awaitItem() are missing), so I think it's fine, do you agree?

[jmartinesp]

This has the side effect of not displaying the actual error when something unexpected happens in the tests related to the state values, instead displaying an error saying it can't print the actual error because it doesn't know how to debug-print the state value because it doesn't have the kotlin reflection library.

When we have such issue in the test, we now know that it's because there are unconsumed state(s) (some awaitItem() are missing), so I think it's fine, do you agree?

We do, but it's not the first time - and won't be the last - I've had to tell some contributor why that happened (ask @richvdh ). If we can fix it with adding the library just for the unit tests it seems like a good trade-off.

[jmartinesp]

It seems like just adding the lib doesn't fix the mentioned issue. It's ok then, let's just merge this and we can later iterate on it.