generated from adobe/aem-boilerplate
-
Notifications
You must be signed in to change notification settings - Fork 177
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
MWPW-151790[MILO][MEP] Organize getPersConfig function in personalization.js #2454
Merged
Merged
Changes from 8 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c3b1675
replace overridePersonalizationVariant function
markpadbe 06d62a1
Fix chaining
markpadbe ee8a2f5
Move parseMepParam
markpadbe c027c7d
Merge branch 'stage' into mepplaceholdersfix
markpadbe 13239e9
add additional optional chaining operator
markpadbe 96d95a0
Merge branch 'stage' into mepplaceholdersfix
markpadbe 2ae612c
Refactor personalization.js
markpadbe 14cfa36
Remove comment
markpadbe facdd89
Merge branch 'stage' into orggetpersconfigfrommepplaceholderfix
markpadbe 36129d0
Add back in deleted variants
markpadbe File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this one is the only business logic change. Everything else is a name swap. Is this prop dele intentional ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, this is intentional. I just updated the comment to mention it. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markpadbe I hate to say it, but let's not remove. I forgot about this use of the object. We're essentially trying to take the decision from the Target instance and merge it with the fresh data of the imported instance (when there's a duplicate). So I worry if we delete the variants we create a small fringe case of deleting it and then needing it later in the loop.