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

[angular-xmcloud][xmcloud-proxy] Personalization support #1964

Merged
merged 31 commits into from
Nov 7, 2024

Conversation

art-alexeyenko
Copy link
Contributor

@art-alexeyenko art-alexeyenko commented Nov 6, 2024

Description / Motivation

Adds personalization and A/B testing support into angular-xmcloud setup.
Personalization works through xmcloud-proxy and should allow for personalization support for react and vue in future.

Testing Details

  • Unit Test Added
  • Manual Test/Other (Please elaborate)

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)

@art-alexeyenko art-alexeyenko changed the title [angular-xmcloud][xmvloud-proxy] Personalization support [angular-xmcloud][xmcloud-proxy] Personalization support Nov 6, 2024
@art-alexeyenko art-alexeyenko requested a review from a team November 6, 2024 05:51
Copy link
Contributor

@yavorsk yavorsk left a comment

Choose a reason for hiding this comment

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

Great work! :)

could not find anything significant, just few minor things - one of which to fix the build - otherwise approve from me!

@yavorsk
Copy link
Contributor

yavorsk commented Nov 6, 2024

One more thing - do we need some migration instructions to the upgrade guide?

@art-alexeyenko
Copy link
Contributor Author

@illiakovalenko @yavorsk Addressed your comments, please take a look.
In regards to upgrade guide, I added some light instructions. Otherwise, there's not much to instruct, right? Xmcloud proxy is a new product, users would simply need to make the switch and start using it.

@illiakovalenko
Copy link
Contributor

@art-alexeyenko Can you, please, check code coverage as well? use "npm run coverage", I've seen that code snippets are not covered

Copy link
Contributor

@illiakovalenko illiakovalenko left a comment

Choose a reason for hiding this comment

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

Approved in advance! Great progress, it looks cleaner now 👍
See one comment below and revert the piece that produces breaking changes personalize/layoutPersonalizer

@art-alexeyenko art-alexeyenko merged commit 456b9df into dev Nov 7, 2024
1 check passed
@art-alexeyenko art-alexeyenko deleted the feature/jss-3529-angular-personalize branch November 7, 2024 19:46
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