Pierre Theo Klein

Yep. That makes sense. And then we can also load those fields automatically to the frontend instead of storing it in the constants file.

The application already has the name of the PDF. The name of the PDF is the timestamp followed by the hacker ID.

This is going to be a Herculean task, but def worth it. I would recommend creating a new branch to work on this, with many PRs going into that new...

You can add & export an interface as a separate file and then import it into both files you want to use it. We do this for other interfaces too!

There's a 2+ year old PR which displayed some data. Not sure if it's worth going through that when working on this issue

Which pdf did you try to download?

The name of the PDF looks to be the base64 data of the pdf itself... I wonder if we can explicitly change the name of the pdf.

This seems like a really important unaddressed issue :(

Haven't looked into the issue, but this webpage might be helpful. 1. https://dev.to/flexdinesh/cache-busting-a-react-app-22lk 2. https://webpack.js.org/guides/caching/

Through the stack, there are several separate requests for hacker info. Since hacker info isn’t cached when we get an error on response, there will be several requests along with...