Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow past games to be viewable on the website #126

Open
tso opened this issue Nov 23, 2018 · 0 comments
Open

Allow past games to be viewable on the website #126

tso opened this issue Nov 23, 2018 · 0 comments
Assignees
@tiffanynwyeung
Labels
issue: feature request For issues only. Marks reported feature suggestions. medium priority For PRs & issues. Marks issues/fixes for said issues that we prefer implemented sooner than later. stack: backend For PRs & issues. Describes what part of the codebase the issue/code affects. stack: frontend/UI For PRs & issues. Describes what part of the codebase the issue/code affects.

Comments

@tso
Copy link
Contributor

tso commented Nov 23, 2018

Let's solidify our URL assumptions: dashboard/* assumes we are talking about the most recent game
and requires a running game.

We probably want to have a /games (or some other name, doesn't matter to me) view with subpages like /games/<game uuid>/zombie-tree.

We probably also want to somehow hook up mission/announcements history, but that might be a bit painful.

Perhaps make past games viewable only by those who participated in them? Not sure!
@tso tso added the issue: feature request For issues only. Marks reported feature suggestions. label Nov 23, 2018
@tiffanynwyeung tiffanynwyeung added medium priority For PRs & issues. Marks issues/fixes for said issues that we prefer implemented sooner than later. type: improvement For PRs only. Marks PRs that refactor/improve on working, existing code. labels Nov 24, 2018
@tiffanynwyeung tiffanynwyeung added stack: backend For PRs & issues. Describes what part of the codebase the issue/code affects. stack: frontend/UI For PRs & issues. Describes what part of the codebase the issue/code affects. and removed type: improvement For PRs only. Marks PRs that refactor/improve on working, existing code. labels Mar 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tiffanynwyeung tiffanynwyeung

Labels
issue: feature request For issues only. Marks reported feature suggestions. medium priority For PRs & issues. Marks issues/fixes for said issues that we prefer implemented sooner than later. stack: backend For PRs & issues. Describes what part of the codebase the issue/code affects. stack: frontend/UI For PRs & issues. Describes what part of the codebase the issue/code affects.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tso @tiffanynwyeung