generated from openedx/frontend-template-application
-
Notifications
You must be signed in to change notification settings - Fork 148
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
fix(deps): update dependency @optimizely/react-sdk to v3 #1200
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/optimizely-react-sdk-3.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
5 times, most recently
from
March 20, 2024 13:33
87b7ee3
to
75f183a
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
4 times, most recently
from
April 3, 2024 06:31
588e71a
to
842d296
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1200 +/- ##
=======================================
Coverage 87.69% 87.69%
=======================================
Files 124 124
Lines 2299 2299
Branches 646 646
=======================================
Hits 2016 2016
Misses 274 274
Partials 9 9 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
7 times, most recently
from
April 11, 2024 13:22
06c70a8
to
b2b3e00
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
from
April 19, 2024 05:57
b2b3e00
to
56c4294
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
2 times, most recently
from
May 3, 2024 05:29
de94427
to
b947e4a
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
9 times, most recently
from
June 18, 2024 12:04
75ab06a
to
5cb5909
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
3 times, most recently
from
July 1, 2024 22:17
bc6b7f7
to
1e06723
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
4 times, most recently
from
July 9, 2024 12:50
7a02f93
to
4d33d6e
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
5 times, most recently
from
July 22, 2024 07:28
344c7b9
to
f589a41
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
7 times, most recently
from
August 28, 2024 10:11
631a5b7
to
a9ba30a
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
2 times, most recently
from
September 2, 2024 10:48
60514fa
to
74a440a
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
from
September 10, 2024 11:52
74a440a
to
9a8bb33
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
from
September 20, 2024 14:33
9a8bb33
to
0fae1ff
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
4 times, most recently
from
September 23, 2024 01:46
8934bb7
to
11e7cc2
Compare
renovate
bot
force-pushed
the
renovate/optimizely-react-sdk-3.x
branch
from
September 23, 2024 04:40
11e7cc2
to
8c61880
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 contains the following updates:
^2.9.1
->^3.0.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
optimizely/react-sdk (@optimizely/react-sdk)
v3.2.2
Compare Source
Bug fixes
v3.2.1
Compare Source
Bug fixes
clientReady
is true even though internal client promise returnssuccess == false
bug fix(#273)useDecision
hook set the update listener on overy render bug fix(#273)setForcedDecision
does not reflect the changes in optmizely instance anduseDecision
hook bug fix(#274)Changed
v3.2.0
Compare Source
New Features
useTrackEvent
hook is now available for tracking events within functional components. This hook offers all the existing track event functionalities provided by the SDK. (#268)v3.1.2
Compare Source
Changed
v3.1.1
Compare Source
Bug Fixes
v3.1.0
Compare Source
Bug Fixes
(#255)
Changed
v3.0.1
Compare Source
Changed
@optimizely/optimizely-sdk
to version5.0.1
(#242)v3.0.0
Compare Source
New Features
The 3.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (
#229,
#214,
#213,
#212,
#208,
#207,
#206,
#205,
#201,
#200,
#199)
You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.
With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Customer Success Manager.
This release leverages the Optimizely JavaScript SDK 5+
This version includes the following changes:
New APIs added to
ReactSDKClient
:fetchQualifiedSegments()
: this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.getUserContext()
: get the currentOptimizelyUserContext
object in use at the React SDK level.getVuid()
: provides access to the anonymous client-side visitor ID (VUID) generated by the JS SDK. This ID is used to identify unique visitors in Optimizely Results in the absence of a standard user ID.sendOdpEvent()
: customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.For details, refer to our documentation pages:
Advanced Audience Targeting
Client SDK Support
Initialize React SDK
Advanced Audience Targeting segment qualification methods
Send Optimizely Data Platform data using Advanced Audience Targeting
Breaking Changes
102.0
.84.0
.91.0
.76.0
.13.0
.16
.Changed
@optimizely/optimizely-sdk
to version5.0.0
(#230).@optimizely/js-sdk-*
packages.Bug Fixes
OptimizelyProvider
to (#229)userId?
anduser?
interface fields, using theDefaultUser
to signal to client-side contexts to use the newvuid
identifier.Configuration
📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.