Feature/sort megacards from newest to oldest #90
Merged
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.
Problem
Resolves: Sort megacards from newest to oldest
Solution
@meganrm has added a
dateCreated
timestamp for each megaset in the test database, so the megasets are now sorted from newest to oldest before being rendered as megacards. (The plan is to modify the Firebase scripts soon so that the timestamps are added automatically for newly uploaded datasets)Type of change
Please delete options that are not relevant.
Change summary:
Steps to Verify:
npm run start:test-db
Screenshots (optional):
Thanks for contributing!