Wren

This is a great idea. Unfortunately not all platforms provide projected data, so it might have to be on as-available basis. For instance, Yahoo outsources their projections to a third...

@mille5a9 thanks for chiming in with the data structure info. @AsteroidOrangeJuice it seems you've caught a typing documentation error on my part... the representation of `List[Dict[str: Team]]` is actually the...

@AsteroidOrangeJuice YFPY 8.0.8 now includes updated documentation to properly reflect the expected data structures. I still think an overall cleaner solution would be the best approach, but at least in...

Closing this as I don't think there are any outstanding related issues. Please feel free to re-open if that is not the case.

Handling all variations of different platform playoffs is not currently a realistic goal, closing for now.

Hi @h-r-x, thanks for the bug report. I just tried generating a report for a private ESPN league using v16.0.1 (the latest published version), and it worked without issue. There...

@h-r-x did your league start in week 1 or a later week? Also, on line 329 of `dao/platforms/espn.py`, could you add `print(matchups_by_week)` in share the output? Your stack trace seems...

> When I run the file Were you trying to run _only_ that file? My apologies if I was unclear, what I meant was for you to add the print...

Yeah now that I know it's a 7 team league with bye weeks, I'm positive _that_ is the reason you're getting your error. As I mentioned, I have never had...

Great idea... it would be nice to just do away with all of the separate auth files (for the various platforms and integrations) and just have them all in the...