New Endpoints + General Endpoint Groupings

[slyyyle]

Hi all,

First off I really appreciate your work on this repo, it has been such a fun thing to use for my personal project. I saw some new endpoints added as I was looking for a schedule based endpoint. It got me thinking, there's a general structure, and you've documented usage of these endpoints quite well as well as package structure mapped out. But, is there any "general usage" documentation regarding which endpoints are typically used together, etc? I would love to help out with this when I get the opportunity, as I've been looking for something like this myself. I've found that certain player dashboards have the same endpoints, and same outputs, and therefore fit well in a front end together - etc.

I imagine this has implications for number of API calls as well, understanding how this overlap exists!

Thank you so much.

-slyle

[slyyyle]

I also would love instruction on keeping endpoint analysis up to date, or perhaps I missed the docs. I am essentially trying to circumvent having to grab get_dict() for some of the complex boxscores, which means I have to pull the metadata or "schema" from the endpoint analysis file, which for now I've saved a hardcoded copy of one from 5 months ago, but it seems to be missing BoxScore endpoints.

-I do this for ease of use with more nested objects.
-I lump certain dataframes together using a react data grid that can dynamically init based on information from the data object. However, I couldn't find the name of each dataframe as the return of get_data_frames() is a list of dataframes, naturally. This "grouping" of data frames for a personal front end app makes navigation and EDA much easier - this becomes problematic for "like" endpoints that have different params or expected JSON response structures.

Thanks!

[rsforbes]

@slyyyle - Please post your code.