[Backend Cleanup] Fix ESLint Issues in apps/backend/src/routes/analytics.ts

[Harxhit]

Title

[Backend Cleanup] Fix ESLint Issues in apps/backend/src/routes/analytics.ts

Summary

Fix lint and code-style issues only in apps/backend/src/routes/analytics.ts to improve backend code consistency, maintainability, and compliance with the existing ESLint configuration.

Contexts

The backend currently contains multiple lint violations across route files. This issue is intentionally scoped to a single file:

apps/backend/src/routes/analytics.ts

Current lint issues reported for this file include:

• Missing explicit return type
• Unused reply parameter
• Minor ESLint cleanup

This is strictly a backend cleanup task and does not involve adding features, changing API behavior, or modifying analytics logic. :contentReference[oaicite:0]{index=0}

Scope Restrictions

Please follow these restrictions carefully:

Allowed File

Only modify:

apps/backend/src/routes/analytics.ts

Do Not

• Modify any other backend route files
• Modify Prisma schema or database files
• Modify authentication logic
• Refactor unrelated code
• Add new features
• Change analytics behavior or API response shape
• Submit multi-file lint cleanup PRs

PRs touching unrelated files may be requested for revision.

Tasks

• Fix lint issues in apps/backend/src/routes/analytics.ts
• Add missing explicit return types where required
• Resolve unused reply parameter warnings
• Ensure changes remain scoped only to analytics.ts
• Run lint verification before submitting PR

Acceptance Criteria

• Only apps/backend/src/routes/analytics.ts is modified
• apps/backend/src/routes/analytics.ts passes ESLint without errors
• No API or analytics functionality is changed
• Changes remain limited to lint and code-quality cleanup only
• PR includes pnpm lint proof (terminal output or screenshot)

Verification Command

Run and attach proof using:

pnpm lint

Area

backend

Difficulty

easy / good-first-issue / cleanup

[qorexdevs]

i can take this one.
plan: keep changes only in apps/backend/src/routes/analytics.ts, fix return type + unused reply lint warnings, then run pnpm lint and attach the proof in PR.

[aarju-s]

Hi @Harxhit I'm a GSSoc'26 contributor. Can you please assign this to me !

[SMishra-27]

Hi @Harxhit

I’d like to work on this issue as part of GSSoC’26.

Proposed Approach

I will keep the changes strictly scoped to "apps/backend/src/routes/analytics.ts" as mentioned in the issue guidelines.

Planned steps:

• Inspect the current ESLint warnings/errors in "analytics.ts"
• Add explicit return types wherever required for better type safety and consistency
• Resolve unused parameter warnings (such as the unused "reply" parameter) without affecting route behavior
• Perform minor lint/code-style cleanup while preserving the existing analytics logic and API response structure
• Verify that no unrelated files are modified
• Run "pnpm lint" locally and attach proof in the PR submission

I’ll ensure the contribution remains cleanup-focused only and fully follows the project restrictions.

[anuragbraveboy-sudo]

Hey @Harxhit! 👋

I'd love to work on this issue under GSSoC'26!

My Approach:

• Run ESLint on apps/backend/src/routes/analytics.ts
• Fix all lint errors (unused vars, type issues, formatting)
• Run pnpm lint to verify all errors are resolved
• Keep existing logic untouched — only cleanup

I've already contributed to this repo (PR #182) so I'm familiar with the codebase. Ready to start immediately! 🙏

[qorexdevs]

Stepping back from this issue to keep the queue clean since there are already multiple active claimants.