Validate Analytics Range Parameter and Return 400 for Unsupported Values

[jikrana1]

Description

Problem

The getTrends endpoint silently falls back to the default daily range whenever an unsupported range value is provided.

This behavior hides client-side mistakes and makes debugging more difficult because invalid requests still return successful responses.

Proposed Solution

• Validate the range query parameter.
• Accept only daily, weekly, and monthly.
• Return HTTP 400 Bad Request for unsupported values.
• Include a clear validation message listing the supported range values.
• Remove the silent fallback behavior.

Benefits

• Improves API validation.
• Makes debugging easier.
• Prevents unintended analytics results.

[github-actions]

👋 Welcome back! Thanks for your continued contribution. Your issue/PR is received and waiting for maintainer review.

[github-actions]

The issue highlights a problem with the getTrends API endpoint, which currently defaults to a daily range when an unsupported range parameter is provided, leading to silent errors and debugging challenges. The proposed solution is to validate the range parameter, only accepting daily, weekly, or monthly, and to return a clear HTTP 400 error with a message listing accepted values if invalid input is detected, thereby improving API validation and debugging.

[jikrana1]

please assign to me this issue .