The Wayback Machine - https://web.archive.org/web/20201016135131/https://github.com/segmentio/analytics.js-integrations/pull/501
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

Release #481 (refactor: Clean up the Optimizely integration) #501

Open
wants to merge 6 commits into
base: master
from

Conversation

@tysonmote
Copy link

@tysonmote tysonmote commented Aug 10, 2020

What does this PR do?

Releases #481, contributed by Optimizely.

Are there breaking changes in this PR?

See #481

Any background context you want to provide?

See #481

Is there parity with the server-side/android/iOS integration components (if applicable)?

N/A

Does this require a new integration setting? If so, please explain how the new setting works

No.

Links to helpful docs and other external resources

See #481

@tysonmote tysonmote self-assigned this Aug 10, 2020
nchilada and others added 6 commits Jun 12, 2020
* Don't attempt to interface with Optimizely Classic Web, since Classic is finally dead
* Prepare to support Optimizely Edge, an alternative to Optimizely Web
* Drop all references to customCampaignProperties. It seems to have been documented [here](https://segment.com/docs/connections/destinations/catalog/optimizely-web/#settings) but it couldn't possibly have worked.
* Generally refactor the code and tests.
@tysonmote tysonmote force-pushed the clean-up-optimizely-integration branch from d0e1e56 to 380f024 Aug 10, 2020
@tysonmote tysonmote requested review from briemcnally and gpsamson Aug 10, 2020
@gpsamson
Copy link
Contributor

@gpsamson gpsamson commented Aug 11, 2020

Hey @tysonmote! I'll follow along in #481 and give both this PR and the original PR a 🟢 when those linting fixes are pushed. :)

@nchilada
Copy link

@nchilada nchilada commented Aug 13, 2020

Thank you so much for taking this!

As a heads up, we have a few more PRs coming down the pike. I think a rebased version of #479 #483 will be the first one to add new customer-facing functionality after #481 is merged. From our point of view, releasing #481 on its own doesn't do a whole lot, except maybe to derisk the following releases. Just letting you know in case it saves you some work this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.