-
Notifications
You must be signed in to change notification settings - Fork 170
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
Add alliance details to team detail page #5937
base: py3
Are you sure you want to change the base?
Add alliance details to team detail page #5937
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## py3 #5937 +/- ##
==========================================
- Coverage 93.10% 92.88% -0.22%
==========================================
Files 658 659 +1
Lines 42145 42670 +525
Branches 60 60
==========================================
+ Hits 39241 39636 +395
- Misses 2896 3026 +130
Partials 8 8 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome. The new typing renaming and organization make a whole lot of sense. A few questions/comments
@@ -188,7 +235,7 @@ <h4>District Points Earned</h4> | |||
<p class="muted">No matches played.</p> | |||
{% else %} | |||
<p class="muted">No matches yet. Check back after {{ comp.event.start_date|strftime("%B %d, %Y") }}.</p> | |||
{% endif %} | |||
{% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stray space?
event.event_type_enum, event.year | ||
) | ||
|
||
alliance, alliance_pick = AllianceHelper.get_alliance_details_and_pick_name( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
get_known_alliance_size
is called within this helper. Would it make sense to remove the redundant call above and have get_alliance_details_and_pick_name
also return alliance_size
?
|
||
alliance_size = cls.get_known_alliance_size(event.event_type_enum, event.year) | ||
|
||
for alliance_check in none_throws(event.alliance_selections): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if either of the if
statements below match, we should be able to break out of the for loop right?
This PR provides details about Alliance Selection and that Alliance's progression.
Motivation and Context
I often find myself switching back and forth between event pages and alliance pages to determine an team's alliance, and find that the data should just be presented inline.
How Has This Been Tested?
There seem to be no automated tests for the team renderer, so no automated tests were done. Manual tests were done with:
Screenshots (if appropriate):
Types of changes