Skip to content

fix: check feature flag api is available #1308

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

Merged
merged 4 commits into from
Sep 18, 2024
Merged

fix: check feature flag api is available #1308

merged 4 commits into from
Sep 18, 2024

Conversation

sareyu
Copy link
Collaborator

@sareyu sareyu commented Sep 17, 2024

CI Results

Test Status: ⚠️ FLAKY

📊 Full Report

Total Passed Failed Flaky Skipped
124 117 0 7 0

Bundle Size: ✅

Current: 78.96 MB | Main: 78.96 MB
Diff: +0.98 KB (0.00%)

✅ Bundle size unchanged.

ℹ️ CI Information
  • Test recordings for failed tests are available in the full report.
  • Bundle size is measured for the entire 'dist' directory.
  • 📊 indicates links to detailed reports.
  • 🔺 indicates increase, 🔽 decrease, and ✅ no change in bundle size.

@sareyu sareyu marked this pull request as ready for review September 17, 2024 13:16
Comment on lines 34 to 36
export const useFeatureFlags = () => {
return useGetFeatureVersion('/viewer/feature_flags') > 1;
};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for me, hook naming isn't 100% clear, I'd call it like useFeatureFlagsAvailable

@sareyu sareyu merged commit 8531b95 into main Sep 18, 2024
6 checks passed
@sareyu sareyu deleted the issue1296 branch September 18, 2024 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Diagnostics] Display Configs tab only if endpoint available in capabilities
2 participants