-
Notifications
You must be signed in to change notification settings - Fork 941
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
[BUG] Standings W-L Issue #179
Comments
The power rankings graph and the managers tab also do not seem to align. |
Do you mind posting some screenshots of the mismatch and your league's website? |
I also added the managers tab as they don't seem to align with the power rankings order. |
I have this problem too and after some debugging, I believe the |
I have an update coming out (#181) that I believe fixes this just due to revised implementation. I'm hoping to release it within the next week or two. |
@nmelhado I synched the change from #185 into my repo and was still able to reproduce this bug by following the steps in my previous comment. For the time being, I've implemented a small change to the |
Ah ok, I was hoping it was fixed due to how team names are being shown. I'll work on a fix for this. Seems like the sort is a little brittle, so I might just move away from that and turn rosters into an object. Might be slightly more work, but it should prevent similar issues from happening again. |
@lrtoenjes this should actually fix it. Sorry for the false fix the first time. If there are still issues, let me know! |
Describe the bug
The standings tab doesn't seem to populate the W-L records correctly to each team. It looks like the values are correct but not assigned to the proper manager.
Your League ID
866130738192539648
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Correct W-L assigned to proper manager.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: