-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qualifying/Sprint Endpoint: "fastest" and "status" filter return no data when used #9
Comments
This is only partially fixed. The current situation is Qualifying
Sprint
Race |
Sorry to reopen again, but this is still problematic. The problem is not quite the same but very related, therefore I'll reuse this issue. Some definitions first, for clarification, because these filters can be a bit confusing.
All of these filters work fine on their own, but some of them don't work in combination. What is currently not working is
All other combinations work fine. |
Also noting #10 that is fixed but related |
When using the "fastest" or "status" filter in combination with the
/qualifying
endpoint, no data at all is returned.These filters work with data from the race results (fastest lap in the race and finishing status in the race respectively).
Example:
http://api.jolpi.ca/ergast/f1/2023/fastest/1/qualifying.json
http://ergast.com/api/f1/2023/fastest/1/qualifying.json
I have to say that this is a rather unusual way to filter the qualifying results. Therefore, if this is difficult to fix, I'd vote in favour of not supporting these filters on this endpoint.
The text was updated successfully, but these errors were encountered: