refactor: migrate get features + remove datadog widget#7093
refactor: migrate get features + remove datadog widget#7093
Conversation
There was a problem hiding this comment.
Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.
Once credits are available, reopen this pull request to trigger a review.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Docker builds report
|
Playwright Test Results (oss - depot-ubuntu-latest-16)Details
Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
|
|
|
||
| const { data: featureListData, isFetching: isLoadingFeatures } = | ||
| useGetFeatureListQuery( | ||
| apiParams ? { ...apiParams, identity: id } : ({} as any), |
There was a problem hiding this comment.
Since skip already prevents the query from firing, is the {} as any fallback needed here?
| setCurrentFeatureStates(FeatureListStore.getEnvironmentFlags()) | ||
| } | ||
| FeatureListStore.on('change', callback) | ||
| const { getEnvironmentIdFromKey, isLoading: _isLoadingEnvs } = |
There was a problem hiding this comment.
Noticed FeatureExport.tsx uses isLoadingEnvs in its loading state but FeatureImport.tsx doesn't — is that intentional?
talissoncosta
left a comment
There was a problem hiding this comment.
Just some comments, not blockers. Thanks for handling that @kyle-ssg
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
How did you test this code?