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

staging -> main (Core 3.0.1/ Lifecycle 3.0.1/ Identity 3.0.1) #673

Merged
merged 42 commits into from
May 23, 2024

Conversation

yangyansong-adbe
Copy link
Contributor

No description provided.

prudrabhat and others added 30 commits April 3, 2024 12:12
- Also replace deprecated test method.
Update LaunchRuleTransformer.kt
Fix event history logs
Currently, presentation delegate notifies only the url's
opened by the UriService which is a regression from 2.x.

Change the logic to make UiService handle both uri's and url's
if the event listener is unable to handle them. Further, notify
PresentationDelegate of all uri's opened as part of the interaction.
Currently AEPUIService creates a coroutine scope for every
presentable to avoid one workflow distuption cancelling another.

Instead we can use a combination of SupervisorJob and a Coroutine
execption handler to use the same coroutine scope for all operations
on main thread by UIService, while ensuring that the disjoint interactions
do not interfere with each other.
Currently, screen shize related calculations are done once
and remembered on recompositions. This works well when adapting
to the new size when orientation of the device is changed.

However, when the activity hosting the composable restricts configuration
changes, the remembered value is not recomputed preventing the presentables
from adapting to the new screen size.

As a solution, do not remember the size related calculation. Always calculate
them on composition.
…ation

Notify PresentationDelegate on all webview uri's
Always recompute screen size related calculations
@yangyansong-adbe yangyansong-adbe marked this pull request as ready for review May 23, 2024 21:01
Copy link

codecov bot commented May 23, 2024

Codecov Report

Attention: Patch coverage is 89.51613% with 13 lines in your changes are missing coverage. Please review.

Project coverage is 81.55%. Comparing base (e8ebb95) to head (6b49406).
Report is 2 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #673      +/-   ##
============================================
+ Coverage     81.42%   81.55%   +0.13%     
- Complexity     2123     2133      +10     
============================================
  Files           191      191              
  Lines          8913     8904       -9     
  Branches       1114     1111       -3     
============================================
+ Hits           7257     7261       +4     
+ Misses         1102     1089      -13     
  Partials        554      554              
Flag Coverage Δ
functional-tests 27.75% <57.26%> (+0.19%) ⬆️
unit-tests 68.88% <42.74%> (+<0.01%) ⬆️

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

Files Coverage Δ
...be/marketing/mobile/internal/util/MapExtensions.kt 81.82% <100.00%> (-6.42%) ⬇️
...be/marketing/mobile/internal/util/SetExtensions.kt 100.00% <100.00%> (ø)
...mobile/launch/rulesengine/LaunchRuleTransformer.kt 93.10% <100.00%> (-1.49%) ⬇️
...adobe/marketing/mobile/services/ui/AEPUIService.kt 87.88% <100.00%> (+2.16%) ⬆️
...eting/mobile/services/ui/alert/AlertPresentable.kt 40.74% <100.00%> (+2.28%) ⬆️
...keting/mobile/services/ui/common/AEPPresentable.kt 94.16% <100.00%> (ø)
...ces/ui/floatingbutton/FloatingButtonPresentable.kt 59.38% <100.00%> (+1.31%) ⬆️
...services/ui/floatingbutton/views/FloatingButton.kt 75.81% <100.00%> (ø)
...mobile/services/ui/message/views/MessageContent.kt 92.59% <100.00%> (-1.75%) ⬇️
...hone/java/com/adobe/marketing/mobile/Identity.java 92.39% <ø> (ø)
... and 10 more

... and 3 files with indirect coverage changes

@yangyansong-adbe yangyansong-adbe merged commit 55d1790 into main May 23, 2024
9 checks passed
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.

5 participants