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

SUP-2582, Upcoming SRMs should be ordered by most recent date #541

Merged
merged 2 commits into from
Nov 6, 2015

Conversation

vikasrohit
Copy link
Contributor

-- Fixed sorting in dashboard (ascending by registrationStartAt)
-- Fixed sorting in My SRMs#Upcoming (ascending by codingStartAt)
-- Fixed sorting in My SRMs#Past (ascending by codingEndAt)

@parthshah @oyeanuj fyi

-- Fixed sorting in dashboard (ascending by registrationStartAt)
-- Fixed sorting in My SRMs#Upcoming (ascending by codingStartAt)
-- Fixed sorting in My SRMs#Past (ascending by codingEndAt)
@@ -21,7 +21,7 @@

function getSRMs() {
var params = {
filter: 'status=future',
filter: 'status=future&orderBy=registrationStartAt',
Copy link
Contributor

Choose a reason for hiding this comment

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

'orderBy' is not a filter. It should be passed as a separate param like 'limit'

@parthshah parthshah closed this Nov 6, 2015
@parthshah parthshah reopened this Nov 6, 2015
@vikasrohit
Copy link
Contributor Author

Incorporated changes. Please review.

@parthshah
Copy link
Contributor

Looks good. Thanks!

parthshah added a commit that referenced this pull request Nov 6, 2015
…y-registration-start

SUP-2582, Upcoming SRMs should be ordered by most recent date
@parthshah parthshah merged commit 43fdb74 into master Nov 6, 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.

2 participants