Skip to content
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

[front] - fix(analytics): workspace analytics #11518

Merged
merged 2 commits into from
Mar 21, 2025

Conversation

JulesBelveze
Copy link
Contributor

Description

This PR fixes the way we access the number of active users in the workspace analytics

Risk

Low

Deploy Plan

Deploy front

 - Renamed 'last_7_days_active_users' to 'nb_active_users_last_7_days' to better reflect the metric it represents
 - Renamed 'last_30_days_active_users' to 'nb_active_users_last_30_days' for consistent field naming and clarity
 - Added unique keys to React fragments for stable component identity during list rendering
@@ -96,7 +96,7 @@ export const NavigationSidebar = React.forwardRef<
{subNavigation && tab.isCurrent(activePath) && (
<>
{subNavigation.map((nav) => (
<>
<React.Fragment key={`nav-${nav.label}`}>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Bonus: we were hitting a bunch of error logs on the "workspace" tab

Warning: Each child in a list should have a unique "key" prop.

@JulesBelveze JulesBelveze requested a review from adrsimon March 21, 2025 09:56
Copy link
Contributor

@adrsimon adrsimon left a comment

Choose a reason for hiding this comment

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

lgtm!

@JulesBelveze JulesBelveze merged commit e909b0e into main Mar 21, 2025
6 checks passed
@JulesBelveze JulesBelveze deleted the fix/workspace-analytics-display branch March 21, 2025 10:02
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.

2 participants