fix: remove Optimizely and surrounding components #386
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.
This PR accomplishes a few tasks that help to clean up some of the code around initializing Optimizely. This code is left over from an old experiment that should now be done using the frontend-plugin-framework, instead of embedding code directly in the MFE.
What's covered in this PR
@optmizely/react-sdk
dependency and references to SDK keys in.env
filesProductRecommendations
directory — the main component from the old experimentExperimentProvider
componentoptimizelyScript
that is injected into the<Head>
WidgetFooter
— used to render theProductRecommendations
component if the user was in the assigned experiment variantLoadedSidebar
andNoCoursesSidebar
widgets into a singleWidgetSidebar
component — there was some code duplication here that seemed unnecessary