I would like to work on this, @lbrabec

I would also like to work on this issue @lbrabec

@lbrabec, the API response that has been received is

beta_blockers: 0
beta_blockers_proposed: 0
beta_fe: 4
beta_fe_proposed: 0
final_blockers: 4
final_blockers_proposed: 3
final_fe: 0
final_fe_proposed: 0

we can move ahead to separate the data into two objects either from the backend or from the frontend.
Doing this on the frontend won't be scalable I believe, so can we make changes on the API to get a response something like this-

{
  beta: {
    blockers: 0,
    blockers_proposed: 0,
    fe: 4,
    fe_proposed: 0
  },
  final: {
    blockers: 4,
    blockers_proposed: 3,
    fe: 0,
    fe_proposed: 0
  }
}

PR in #15

The API change makes sense, I already talked to @frantisekz about it. Once the change is programmed, it will be while before it lands in production. Meanwhile we'll have to use staging instance at https://packager-dashboard.stg.fedoraproject.org/api/v1/

@lbrabec, Sounds good to me. I'll be moving ahead to make changes as per the data received from staging API.
Can you confirm the API URL of staging, please?

Can you confirm the API URL of staging, please?

Yes, the URL is https://packager-dashboard.stg.fedoraproject.org/api/v1/, if you are experiencing 404 Not Found that is expected, this is just a base URL to which the actual endpoints are appended later. To use staging instance of backend, change the URL in public/env.js.

Got it! Let me move ahead with this!

@lbrabec, Changes are not reflecting on staging.
I'll push changes once I start getting the expected data.

@lbrabec @manishakanyal How can I help you with this component? I would like to contribute to this component.

@lbrabec I will be excited to work on this issue.

fixed by 82838a3