Liam DeVoe
Liam DeVoe
On beatmaps where a user has multiple scores, such as https://osu.ppy.sh/api/get_scores?k=KEY&b=1872396&u=4787150, adding limit=1 will not affect the number of returned scores.
The replay by https://osu.ppy.sh/users/5720161 on http://osu.ppy.sh/b/1623093 gives an empty replay: https://osu.ppy.sh/api/get_replay?b=1623093&u=5720161&k=KEY&m=0 The same replay is also missing replay data when downloaded from the website: http://osu.ppy.sh/scores/osu/2560921524/download
It would be nice to see what first place ranks a user has. For [circleguard](https://github.com/circleguard/circleguard), first place ranks would be prioritized and screened first, since especially in the case of...
we currently (I believe) toss both waitlist and holdfile into the same "waitlist" attribute. These should be split. See https://api.umd.io/v1/courses/CCJS225/sections/0101, which currently has a waitlist of 30 but testudo says...
eg https://api.umd.io/v1/courses/CCJS225/sections/0101 returns: ``` [ { "course":"CCJS225", "section_id":"CCJS225-0101", "semester":"202108", "number":"0101", "seats":"6", "meetings":[ { "days":"TuTh", "room":"1120", "building":"SQH", "classtype":"", "start_time":"9:30am", "end_time":"10:45am" }, { "days":"TuTh", "room":"1120", "building":"SQH", "classtype":"", "start_time":"9:30am", "end_time":"10:45am" } ], "open_seats":"0",...
for eg https://beta.umd.io/#operation/getCoursesById we allow an array of strings to be passed. The proper format to do so is https://api.umd.io/v1/courses/cmsc131,cmsc330. We should state this explicitly somewhere.
the macos specfile [excludes libraries we don't use from being included](https://github.com/circleguard/circleguard/blob/master/gui_mac.spec#L36), which is great, but for some reason the windows specfiles don't do the same. Should investigate if this is...
right now new users who just want to use circleguard as a replay analysis tool for their own replays have to sit through a long tutorial and enter an api...
this will be complicated because we don't currently calculate sliderbreaks, which happen frequently enough that I'm not comfortable adding a combo counter without having them implemented.