-
Notifications
You must be signed in to change notification settings - Fork 134
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
feat: core pacakge for seamless experiment integration #457
Conversation
Based on output from pull request status check: Micro-Learning Topic: Rate limiting (Detected by phrase)Matched on "rate limiting"API requests demand resources such as network, CPU, memory, and storage. The amount of resources required to satisfy a request depends on the user input and endpoint business logic. Not only can this impact the API server performance, leading to Denial of Service (DoS), but it also leaves the door open to authentication flaws such as brute force attacks. Try this challenge in Secure Code Warrior |
Any info on the CodeQL check that is failing? Not sure what to do here. |
Seeing it first time here on this PR. But I'd say we can dismiss for now. The server and route is only used for testing. |
# [8.17.0](v8.16.1...v8.17.0) (2022-02-10) ### Features * Support seamless integration with amplitude experiment SDK ([#457](#457)) ([af8f9d1](af8f9d1))
🎉 This PR is included in version 8.17.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sibling PRs:
Summary
IdentityStore
andAnalyticsConnector
IdentityStore
maintains an in memory user identity (including user properties) which can be listened to for changes.AnalyticsConnector
allows experiment to send automatic exposure events, including setting and unsetting user properties.Checklist