Table of Contents - vainglory-api-0.1.0 Documentation
Classes and Modules
Methods
- ::[] — VaingloryAPI::Region
- ::find — VaingloryAPI::Region
- ::find_region_data — VaingloryAPI::Region
- ::name_error — VaingloryAPI::Region
- ::new — VaingloryAPI::Client
- ::new — VaingloryAPI::Region
- ::new — VaingloryAPI
- ::valid_short_name? — VaingloryAPI::Region
- ::validate_short_name! — VaingloryAPI::Region
- #abbreviation — VaingloryAPI::Region
- #apply_headers — VaingloryAPI::Client
- #endpoint_uri — VaingloryAPI::Client
- #endpoint_url — VaingloryAPI::Client
- #eql? — VaingloryAPI::Region
- #get_request — VaingloryAPI::Client
- #get_request_without_headers — VaingloryAPI::Client
- #link — VaingloryAPI::Client
- #match — VaingloryAPI::Client
- #matches — VaingloryAPI::Client
- #new — VaingloryAPI
- #player — VaingloryAPI::Client
- #players — VaingloryAPI::Client
- #request — VaingloryAPI::Client
- #response — VaingloryAPI::Client
- #samples — VaingloryAPI::Client
- #serialize_response_data — VaingloryAPI::Client
- #serialize_response_metadata — VaingloryAPI::Client
- #status — VaingloryAPI::Client
- #team — VaingloryAPI::Client
- #teams — VaingloryAPI::Client
- #telemetry — VaingloryAPI::Client
- #validate_region — VaingloryAPI::Client