Clarify Team presentation ownership - #55
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Continues GitHub issue #30 with a small presentation-boundary cleanup after PR #54.
_selector_form.htmlto_team_selector_form.html_summary_cards.htmlpartialPreserved behavior
This PR does not change:
team_id,season, orwindowquery behaviorseason-selector.jsScope
The application shell remains entity-neutral. Team pages explicitly own Team/season/window selection, while the summary partial only renders the existing route-provided
summary_cardsdata.No generic frontend/component framework is introduced.
Part of #30.