This repository has been archived by the owner on Oct 12, 2021. It is now read-only.
Return front-end tweaks to application #192
Closed
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
DO NOT MERGE
Don't know what happened but a lot of the work done by the Mozilla fellows for the frontend is missing. This commit seems to be part of it 7716dff.
I imagine in the mist of merging multiple branches and cleaning out leftover code, some commits were either reverted or just removed. For example, all the d3.js / crossfilter.js code is gone and all the table sorting logic was removed. I'm not sure if that was intentional so I'm working on bringing the code back. I was able to at least get the table sorting back, but I'll need to comb through previous commits to get the d3 logic rocking again.