This repository has been archived by the owner on Jul 31, 2020. It is now read-only.
Provide a way to bias the dates parsed to either the past or the future #4
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
day on relative date tests.
Biasing is signaled by setting the `bias` property to `past` or `future` on an object that is passed as the second optional argument to `Date.parse()`.
|
|
|
This isn't something that we're using anymore, so if these changes inspire anyone to implement a similar feature, that's great. |
|
Hi @eric – thanks for the update. |
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.
Biasing is signaled by setting the
biasproperty topastorfutureon an object that is passed as the second optional argument to
Date.parse().This includes all of the cumulative changes I've done so far, as they were all required to get to the point that I could do this.