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

PR 504 - Updates to make changes additive #513

Merged
merged 2 commits into from
Sep 27, 2018
Merged

PR 504 - Updates to make changes additive #513

merged 2 commits into from
Sep 27, 2018

Conversation

kstreeter
Copy link
Collaborator

PR #504 was merged with several breaking changes. This PR updates these changes to make them additive only.

@kstreeter kstreeter added this to the 0.9.6 milestone Sep 25, 2018
@@ -115,7 +115,7 @@
"xdm:marketing": {
"xdm:trackingCode": "marketingcampaign111"
},
"xdm:profileStitching": [
"xdm:profileStitch": [
Copy link
Contributor

Choose a reason for hiding this comment

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

we could also call this profileMerge also as another option, but this is fine. Either way it's confusing with the other field.

@@ -31,6 +31,12 @@
},
"minItems": 1,
"description": "Array of Identities. Condensed, normalized encapsulation of all end user identifiers."
},
"xdm:endUserIDs": {
Copy link
Contributor

Choose a reason for hiding this comment

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

my big worry here is that when we have IdentityMap, we'll have three fields for representing identity here. I get that we'll deprecate the old ones, but just want to document it here on the review.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

understood @harleensahni, we will plan on cleaning up some of these early deprecations before we call 1.0. They are just helping with current limitations in the tooling.

Copy link
Contributor

@cdegroot-adobe cdegroot-adobe left a comment

Choose a reason for hiding this comment

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

Hi Harleen,

This will be a breaking change as it looks like the first PR #444 went into production. The only option we may have here is to set the current property to depreciated and (property burnt). and come up with a new property. See this PR for what they did #505.

@kstreeter
Copy link
Collaborator Author

@cdegroot-adobe, that's what this PR is: it makes the change non-breaking by keeping the original definitions and marking them as deprecated.

@kstreeter kstreeter merged commit 39c3a50 into master Sep 27, 2018
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