-
Notifications
You must be signed in to change notification settings - Fork 360
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/LIVE-3148 Added development/QA tool for feature flags #814
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 77406d0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 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 |
apps/ledger-live-desktop/src/renderer/components/FirebaseFeatureFlags.tsx
Outdated
Show resolved
Hide resolved
apps/ledger-live-mobile/src/screens/Settings/Debug/OpenDebugFeatureFlags.js
Show resolved
Hide resolved
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.
I reviewed the files that touches Firebase setup for now and I'm good with it besides the few comments
Screenshots: ✅
There are no changes in the screenshots for this PR. If this is expected, you are good to go. |
Codecov Report
@@ Coverage Diff @@
## develop #814 +/- ##
========================================
Coverage 47.93% 47.93%
========================================
Files 620 620
Lines 27870 27870
Branches 7174 7174
========================================
Hits 13359 13359
Misses 14453 14453
Partials 58 58
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
apps/ledger-live-desktop/src/renderer/components/FirebaseFeatureFlags.tsx
Outdated
Show resolved
Hide resolved
3644ac2
to
4ef6152
Compare
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.
We need to split the changeset and I have some small questions
apps/ledger-live-desktop/src/renderer/components/FirebaseFeatureFlags.tsx
Outdated
Show resolved
Hide resolved
apps/ledger-live-mobile/src/components/FirebaseFeatureFlags.tsx
Outdated
Show resolved
Hide resolved
4ef6152
to
2590a54
Compare
@Justkant Take a look again when you have a minute :beau: |
2590a54
to
d388bb2
Compare
apps/ledger-live-desktop/src/renderer/components/FirebaseFeatureFlags.tsx
Outdated
Show resolved
Hide resolved
1dd0031
to
c34b469
Compare
c34b469
to
77406d0
Compare
📝 Description
Due to the nature of the integration with firebase it's not easy to test features that work differently depending on the value of a feature flag from firebase. This PR introduces a tool for LLM and a tool for LLD that allows us to locally override the value of the feature flag for that particular app run. The overrides are not persisted between application launches.
It matches partially the https://ledgerhq.atlassian.net/browse/LIVE-3148 task but I leave it to hub and @thomasrogerlux to take over any remaining topics. This should merely allow us to test and dev with changing values for the flags.
❓ Context
ledger-live-desktop
,ledger-live-mobile
,ledger-live-common
https://ledgerhq.atlassian.net/browse/LIVE-3148
✅ Checklist
📸 Demo
🚀 Expectations to reach
There should be no impact on the functionality of the app. When we change the value of a feature it should act as if the value returned from firebase was the one overriden.