@lbrabec, The approach I can think of is going through every key in an object and create new objects which can have data of the two different cases(beta and final in our case).

@manishakanyal Thank you for your email how can I help you with this component?  I know about the frontend but I am not familiar with a backend.  @lbrabec  told me that I can work on any ticket regardless of who is doing it.

@manishakanyal, I spoke with @frantisekz, the API change will be deployed to stg sometime next week, I'll ping you when the deployment is done so you can proceed.

@lbrabec, Perfect!
Thank you!

@frantisekz had some spare cycles and deployed the change to stg right now.

The change is backwards compatible (i.e. there are both "old" and "new" keys in the API response), but that is just temporary so the old code works for others.

@lbrabec, I'll push the changes today.

@lbrabec, I've made the needed changes. Can you have a look at this, please?

Looks good, thanks.

Please rebase on current master (there is conflict you'll need to fix) and squash the commits to one.

@lbrabec, I've fixed the merge conflict and rebased it. Can you have a look at it, please?

:thumbsup: