Save Steam web API spec in repository #57
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change saves the Steam web API spec in a module in the steamapi. This means that people don't need to make a call every time they want the Steam web API to be populated in Steam Interface, and also means that there is now a file that people can look at to see what functions are currently supported and what parameters they accept.
Down the line, it would probably be nice to format the spec better so that it actually defines python classes. This would be more readable and mean that the python functions are better defined.
Additionally, I modified the APIResponse.dict function to recursively convert all APIResponses to dicts, rather than only convert the top level of the APIResponse into a dict.