-
Notifications
You must be signed in to change notification settings - Fork 27
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
refactor: change http-adapter to eager mode #3548
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: ed7f8c3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 36 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Tobi! 🙇
This PR is missing a Jira ticket reference in the title or description. |
🥷 Code experts: emmenko tdeekens, emmenko have most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: To learn more about /:\ gitStream - Visit our Docs |
* refactor: change http-adapter to eager mode * Create cold-lemons-whisper.md * fix: ts-ignore comment position
Summary
We've been to lazy and should be more eager.
Description
After a lot of communication and alignment we realized that being eager on the http-adapter helps drive user expectations.
The background is that we toggle functionality through the http-adapter which is generally available to users. Having a "delayed" appearing through a reload for these functionalities is not ideal. It's acceptable for anything which sits behind LaunchDarkly and there has also the benefit to avoid the flicker.
Followings
The general storyline is also to get flopflip ready for React Suspense finally when time permits.