Skip to content
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

Endpoint change #51

Closed
wants to merge 71 commits into from
Closed

Endpoint change #51

wants to merge 71 commits into from

Conversation

Esterni
Copy link
Owner

@Esterni Esterni commented Jul 28, 2020

This PR closes #50 by making changes to the constants.py URL, the EventResult response object, and the event_results parameters.

@Esterni Esterni self-assigned this Jul 28, 2020
mikeholler and others added 24 commits July 28, 2020 20:40
custid to cust_id
lowername to name_lower
shortname to name_short
SubSessionData.league_id
SubSessionData.league_season_id
SubSessionData.points_type
SubSessionData.reserve_status
SubSessionData.season_name
SubSessionData.season_name_short
SubSessionData.series_name
SubSessionData.series_name_short
SubSessionData.session_name
SubSessionData.special_event_type_text
SubSessionData.time_start
SubSessionData.time_start_sim
SubSessionData.track
SubSessionData.track_config
…ed it. Added parse_encode to objects with newly completed documentation to see the data
XanderRiga and others added 27 commits February 15, 2021 12:13
We previously had the help message inside the error we are raising, but
we really want to be logging that as that is where users will be looking
for help. Inside the error we can just dump the entire response. This
might be absurd and too much content, but it at least allows them to
make decisions based on this if they want.
We currently raise a `UserWarning` when we fail auth which isn't very
descriptive and doesn't tell us what actually failed.
This is a more accurate error for what is actually happening and lets us
save the actual response in case the user wants to do something with it.
Add a check for empty event results
Bump version to 0.1.1 for a release
Fixed issue #74 (string replace is no longer required)
This is how we will model the data we get back from the league standings
endpoint.
This allows us to get the standings for a leage given the league ID and
league season ID. This can take in more parameters, but those are
documented on the URL, and I don't really see the use, so they can be
added later.
This does not include previous and next race, because I think those
might require some more thought, but this does give us the basics for
gettings the seasons for a league.
This lets us get the seasons for a given league so we can use them to
query leaderboard.
This will have `+` in all the spaces, as well as other weird encoding
things that iRacing uses, so we want them removed.
This is how we can get some specific data about a league by ID.
We want to represent all the data we can get from iRacing about leagues.
This only omits the data about images, since we don't have access to
the actual image anyways.
This is how we can get some basic data about a league from an ID.
This was just a typo, looks like a bad copy/paste. `pos` is the field
that represents position.
@Esterni Esterni closed this Mar 13, 2021
@Esterni Esterni deleted the endpoint-change branch March 13, 2021 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change the URL endpoint for event_results as requested by iRacing
7 participants