Skip to content

Dispatch consequence in an rules consequence event if schema type is not eventHistory#766

Merged
spoorthipujariadobe merged 1 commit intoadobe:feature/disqualificationfrom
spoorthipujariadobe:feature/disqualification
Jun 17, 2025
Merged

Dispatch consequence in an rules consequence event if schema type is not eventHistory#766
spoorthipujariadobe merged 1 commit intoadobe:feature/disqualificationfrom
spoorthipujariadobe:feature/disqualification

Conversation

@spoorthipujariadobe
Copy link
Copy Markdown
Contributor

@spoorthipujariadobe spoorthipujariadobe commented Jun 6, 2025

Description

Restore existing behavior of dispatching consequence in a rules response content event for schema type if the detail is not of type https://ns.adobe.com/personalization/eventHistoryOperation

Related Issue

Motivation and Context

For non event history write cases, we still need to dispatch the consequence so Messaging SDK can use it to display in-app message or content card

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@spoorthipujariadobe spoorthipujariadobe changed the title Dispatch consequence in an event for schema type if its not eventHistory Dispatch consequence in an rules consequence event if schema type is not eventHistory Jun 6, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.25%. Comparing base (f752eba) to head (7c7abc8).
Report is 4 commits behind head on feature/disqualification.

Additional details and impacted files
@@                      Coverage Diff                       @@
##             feature/disqualification     #766      +/-   ##
==============================================================
+ Coverage                       75.25%   75.25%   +0.01%     
  Complexity                       2337     2337              
==============================================================
  Files                             217      217              
  Lines                           10891    10894       +3     
  Branches                         1411     1411              
==============================================================
+ Hits                             8195     8198       +3     
  Misses                           2056     2056              
  Partials                          640      640              
Flag Coverage Δ
android-functional-tests 28.16% <0.00%> (-0.01%) ⬇️
android-unit-tests 64.23% <100.00%> (+0.01%) ⬆️

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

Files with missing lines Coverage Δ
...obile/launch/rulesengine/LaunchRulesConsequence.kt 85.35% <100.00%> (+0.16%) ⬆️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Member

@sbenedicadb sbenedicadb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch

Copy link
Copy Markdown
Contributor

@timkimadobe timkimadobe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thank you!

@spoorthipujariadobe spoorthipujariadobe merged commit 153dca0 into adobe:feature/disqualification Jun 17, 2025
23 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.

3 participants