Should there be an additional listings query parameter also hardcoded to 50 or some other sane number to limit the amount of data returned/displayed?
# When it manages to succeed, and not time out due to CloudFire errors:
$ curl 'https://universalis.app/api/North-America/41759?entries=50' | jq -r '.listings | length'
18084
# Again, rolling the dice on if CF will let the request succeed, but:
$ curl 'https://universalis.app/api/North-America/41759?entries=50&listings=50' | jq -r '.listings | length'
50
This is potentially the same as #46, but given the age of that issue and the lack of followup I'm not sure.
Searching for
Savage Aim Materia XI
as aCross-DC
search drops framerate from 135FPS to 2FPS.Changing to another less-popular item (which resulted in 60FPS) and back to
Savage Aim Materia XI
, this time the framerate drops to 10FPS.This is only a problem when viewing the
Market Data
tab, framerate immediately goes back to normal when viewing theCharts
tab.Checking the actual raw data returned from a Universalis API request for
Savage Aim Materia XI
shows that there are 18,804 results, even withentries
limited to50
per the hard-coded value in: https://github.com/fmauNeko/MarketBoardPlugin/blob/4194ef1295ffb90d854caf08fef34a7889e3d6a1/MarketBoardPlugin/GUI/MarketBoardWindow.cs#L1172-L1178Should there be an additional
listings
query parameter also hardcoded to50
or some other sane number to limit the amount of data returned/displayed?This is potentially the same as #46, but given the age of that issue and the lack of followup I'm not sure.