Skip to content
This repository was archived by the owner on Mar 4, 2025. It is now read-only.

added links #622

Merged
merged 7 commits into from
Dec 23, 2015
Merged

added links #622

merged 7 commits into from
Dec 23, 2015

Conversation

tladendo
Copy link
Contributor

.ended-on #[span {{srm.codingEndAt | localTime:"MMM DD, YYYY" }}]

.member-stats
p.points #[span {{srm.result.finalPoints }}] #[span Points]
.ranks
.division
a.division(href="https://community.{{DOMAIN}}/stat?c=round_stats&rd={{srm.rounds[0].id}}&dn={{srm.result.division}}")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do SRMs always have at least one round with an id and a result property with a division property? If not, we may want to handle the logic for this link in the controller that owns this HTML and pass a single, determined value to the link like srm.roundId. But it may be unnecessary if the API always returns those values :)

@vikasrohit
Copy link
Contributor

@tladendo I think we are missing the division and room links in list view of the srm-tile.

tladendo added a commit that referenced this pull request Dec 23, 2015
@tladendo tladendo merged commit 9b62668 into dev Dec 23, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants