This repository has been archived by the owner on Jul 21, 2019. It is now read-only.
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.
This is an MVP attempt at fixing #291. I think it's enough of an improvement that I'd like to put it in place, though improvements are welcome.
What it gets right:
showing the past events with months/dates makes it much easier to see what happened when (like say, if you wanted to see what month a past event was in, or what events were in a given month)
easier to scan than the giant columns
No longer duplicating future events at the end of the current year
Getting rid of the different way to parse the past events simplifies things.
What is still not ideal:
I would prefer it broken up by years, but that requires saving/comparing state in a way we're not doing right now.
This isn't the DRYest way to code this (but I wanted to repeat myself because I intend to change the "past" more).
This change is