Merge staging into main for Core 3.5.0
#784
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix ordered search type lookup in event history * add failure test case for event history ordered lookup
…re-android into feature/disqualification
* Added handling for insert and insertIfNotExists rule consequence * remove keys look up in event history insert/insertIfNotExists consequence * Dispatch event after insert event history consequence * Tests for insert & insertIfNotExists rule consequence * update API dump * fix failing functional test * fix formatting issues * addressing code review comments * change fnv1a32 to produce 0 hash for empty mask map * fix typo in log * Adding additional tests for invalid event history rules * fix test json content
in API 35. i.e about 6 months ago. This method is automatically treated as no-op on all Android versions since being removed Chromium 119. Also, the in-app message HTML templates provided out of the box for in AJO UI do not use WebSQL. Additionally this technology is not supported since 2010. If the customer does not WebSQL in their webpages, this should not affect them.
…#748) * Adding capability to get content height from html and setting it to webView frame * Updating tests according to the changes * Fixing the functional test * Adding the fitToContent flag with default value true * Changing the approach from evaluateJavascript to handleJavascriptMessage * Addressing the PR comments * Added support for maxWidth in InAppMessageSettings (#753) * Add support for maxWidth in InAppMessageSettings * Update API dump * revert onHeightReceived if check for fitToContent * Add comments to explain maxWidth default value * additional cases and comment fixes in max width tests * fix a few more comments in MessageScreenTests * lint fixes --------- Co-authored-by: Spoorthi Pujari <63024083+spoorthipujariadobe@users.noreply.github.com>
[MOB-22892] Code changes computing webView in accordance with content…
…tion Change ExtensionApi getHistoricalEvents API to be on par with Core iOS
Merge `dev` to `staging` to pick up #767 for Core 3.4.1
Update usages and tests accordingly
* Dispatch consequence in an event for schema type if its not eventHistory * Add support for nested lists to map flattening logic * disable list flattening for ~all_url for backward compatibility * Add more tests and rename existing to maintain uniformity * Separate list and array flattening as extension functions * Unit tests for list and array flattening extension functions * Add entire rule consequence in event dispatched as a result of event history insert * Set newest and oldest occurance to null for event not found in event history
Workflows: - Update workflows to use `gha-android-3.4.1` - Set the staging-dir to match the build artifact directories for individual extensions - Utilize branch ref option to direct snapshots branches Gradle: - Update to use AEP SDK Gradle Plugin 3.4.0 - Fetch from central sonatype snapshots instead of OSS. Makefile: - Switch the `ci-publish-main` and `ci-publish-snapshot` to trigger the publish command.
- Point workflows to gha-android-3.4.2 that fixes build issues
Fix message inset calculation for InAppMessages
Migrate to CentralSonatype publishing
* Dispatch consequence in an event for schema type if its not eventHistory * Add support for nested lists to map flattening logic * disable list flattening for ~all_url for backward compatibility * Add more tests and rename existing to maintain uniformity * Separate list and array flattening as extension functions * Unit tests for list and array flattening extension functions * Add entire rule consequence in event dispatched as a result of event history insert * Set newest and oldest occurance to null for event not found in event history * early escape from insert/insertIfNotExists if event hash is 0
Feature/disqualification -> dev
Updating Core version to 3.5.0
Merge dev into staging for Core 3.5.0
prudrabhat
changed the title
staging into dev for Core 3.5.0staging into main for Core 3.5.0
change event history insert log level
Merge `dev` into `staging` to incorporate #785
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge
stagingintodevfor Core 3.5.0Key changes: