update: update VWO SmartCode to version 2.1 #808
Conversation
This file contains 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
zeeshan-vwo
force-pushed
the
update/vwo-smartcode-v2.1
branch
from
025e7ae to
84ca64b
Compare
zeeshan-vwo
changed the title
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.
What does this PR do?
This PR updates the VWO SmartCode in the project to the latest version (v2.1), replacing the outdated version to ensure compatibility and access to the latest features and improvements.
Are there breaking changes in this PR?
No, there are no breaking changes expected in this PR. The updated SmartCode is backward-compatible with existing functionality.
Testing Plan:
Testing not required
Any background context you want to provide?
The current project contains a very old version of the VWO SmartCode. Upgrading to version 2.1 ensures alignment with VWO’s latest updates and feature set.
Is there parity with the server-side/android/iOS integration components (if applicable)?
This PR is not directly related to server-side, Android, or iOS components.
Does this require a new integration setting? If so, please explain how the new setting works
No new integration settings are required for this update.