Bob Silverberg

@diox Found it! Here's a suggestion for a first step: I can look through code-manager and determine exactly what data is needed for different use cases, and then we can...

I've finished looking through all of our code to see what data is used where. I am going to add some comments to this issue describing some of my findings,...

This was already discussed at https://github.com/mozilla/addons/issues/1822, but I think this could be a major gain: We only need the file entries the first time we retrieve a version, after which...

An issue that discusses potential changes to the way the API deals with file entries has been opened at https://github.com/mozilla/addons/issues/7463.

> I'm not sure we should focus on optimizing which API bits we need or not. This is unlikely to have that much impact, the permissions thing is an outlier,...

It looks like we dealt with the example at https://github.com/mozilla/addons/issues/14131 via https://github.com/mozilla/addons/issues/8339 (Stop exposing license text in versions API). The other example I see here is permissions. We don't limit...

We have discussed, above, whether this is worth worrying about, but I'm not sure we made a final decision. There was a suggestion to track the size of the redux...

@pwalm I came across this as well when I was going to start working on adding the ability to delete a review from the User Profile screen. This list of...

For reference, here's what it looks like on the legacy site: 

@kumar303 While working on mozilla/addons#12280 I noticed that the only information we have about the add-on that corresponds to a review is the `addonId` and `slug`. I guess we'll need...