Skip to content

Harshavarma: Fix job posting analytics not rendering#2151

Open
harshavarma29 wants to merge 1 commit intodevelopmentfrom
harshavarma_job_posting_analytics_not_rendering
Open

Harshavarma: Fix job posting analytics not rendering#2151
harshavarma29 wants to merge 1 commit intodevelopmentfrom
harshavarma_job_posting_analytics_not_rendering

Conversation

@harshavarma29
Copy link
Copy Markdown
Contributor

Description

Fixed the issue where the graph was not rendering and displayed "No data available" for all filters in the development environment.
image

Related PRS (if any):

To test this backend PR, you need to check out the #5102 frontend PR.

How to test:

  1. Check into the current branch
  2. Do npm install and ... to run this PR locally
  3. Check the #5102 frontend PR for testing.

Screenshots or videos of changes:

Week_39_Progress_Video.mp4

@harshavarma29 harshavarma29 changed the title fix: adding api prefix in endpoit of job analytics Harshavarma: fix: adding api prefix in endpoit of job analytics Apr 4, 2026
@harshavarma29 harshavarma29 changed the title Harshavarma: fix: adding api prefix in endpoit of job analytics Harshavarma: Fix job posting analytics not rendering Apr 4, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 4, 2026

Copy link
Copy Markdown

@Rajasrivatsansrinivasan Rajasrivatsansrinivasan left a comment

Choose a reason for hiding this comment

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

Reviewed PR #2151 by Harshavarma along with the related frontend changes. Checked out both branches locally and tested the job posting analytics flow with multiple valid filter combinations and date ranges. The graph is still not rendering and continues to display “No data available,” so the issue does not appear to be fully resolved yet. This needs further investigation before merge.

Image

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