Open YoshiRulz opened 1 year ago
the list can be giant for some games.
the list can be giant for some games.
I assume this was only done for pubs since subs could far outnumber pubs
For reference, this was actually only done for pubs because every additional information we have to show, is additional load for the db for that single page load. So the reasoning that it "saves" a page load does not apply in general. Users not clicking the submission list far outnumber those who do.
the list can be giant for some games.
Yes, it would need to be conditional: use a list if the number of subs (looks to be exposed as Model.Game.SubmissionCount
) is under a threshold, else use the current code.
What's the scenario where seeing submissions right away is critical/important?
Say you knew someone made a submission for game X and you wanted to view it. Going via subs: You can't currently filter subs by game (edit: from that GUI; as feos pointed out to me, the subs link on game pages in fact takes you there with the relevant queryparam populated), but you can filter by system, which should be enough assuming the queue stays under control. Going via games: (this issue). This would just be a small quality-of-life improvement to "game-first" browsing.
This is why I asked how important it is in real life. How often do you have to do the extra click to actually go and see the submission list for a given game? I would say it's rare enough to remain hidden behind a link at all times (no threshold), because overwhelming majority of users only watch publicatons. And even if you don't want to watch the publications, simply checking current branch list for maintenance is more frequent than checking submissions for anything.
I assume this was only done for pubs since subs could far outnumber pubs, but in practice there's often only a few. A simple flat list would save a click / page load.