You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readme currently says "This repository houses the JavaScript SDK for use with Optimizely Feature Experimentation and Optimizely Full Stack (legacy)." but going to the docs over on https://docs.developers.optimizely.com/feature-experimentation/docs/javascript-node-sdk makes it seem pretty clear that this is not a legacy project at all, but the only way to officially do Node based server side optimizely work.
It would be great to explicitly open with what use cases are considered legacy, and what their current counterparts are, before diving into the real README.md
Benefits
clarity in docs.
Detail
No response
Examples
No response
Risks/Downsides
No response
The text was updated successfully, but these errors were encountered:
Pomax
changed the title
[ENHANCEMENT] update readme to explain _what_ is legacy
[ENHANCEMENT] update readme to explain what parts are "legacy"
Dec 18, 2023
Hello @Pomax , actually what is intended is the "Optimizely Full Stack" product is legacy, and "Optimizely Feature Experimentation" is the latest version of the "full stack" experimentation product. . It is not intended to mean that this project itself is legacy. We will look to improve the readme to reflect this. Thanks for bringing this up.
Description
The readme currently says "This repository houses the JavaScript SDK for use with Optimizely Feature Experimentation and Optimizely Full Stack (legacy)." but going to the docs over on https://docs.developers.optimizely.com/feature-experimentation/docs/javascript-node-sdk makes it seem pretty clear that this is not a legacy project at all, but the only way to officially do Node based server side optimizely work.
It would be great to explicitly open with what use cases are considered legacy, and what their current counterparts are, before diving into the real README.md
Benefits
clarity in docs.
Detail
No response
Examples
No response
Risks/Downsides
No response
The text was updated successfully, but these errors were encountered: