-
Notifications
You must be signed in to change notification settings - Fork 156
fix: false flag should not trigger linked flags #1944
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
PR Summary
This PR fixes session recording behavior when dealing with feature flags that are present but disabled, specifically addressing linked flag triggering logic.
- Fixed
LinkedFlagMatching
intriggerMatching.ts
to properly check both flag presence AND value before triggering recording - Added test case in
sessionrecording.test.ts
to verify recording stays in buffering state when linked flag is false - Addresses API behavior change where flags can now be present but disabled (previously only present flags were enabled)
- Critical fix to prevent incorrect session recording activation when feature flags are disabled
2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
Size Change: +90 B (0%) Total Size: 3.4 MB
ℹ️ View Unchanged
|
@marandaneto @ioannisj looks like Android and iOS SDKs don't make this mistake - nice! Do flutter and RN simply use Android and iOS behavior or do I need to look there as well |
Flutter uses Android and iOS, RN has its own flag evaluation, but I think its correct already |
finally a false flag that isn't a conspiracy theory!
it used to be safe to check for the presence of a flag
but we recently started returning flags that are enabled but false
so, it's not safe any more and replay linked flags was broken as a result
i had seen that we changed that API but wrote this code so long ago I totally missed this consequence