Fix usage suggestions for min and max #2946
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
|
Thanks, and sorry for you having to learn the hard way! Related: moment/momentjs.com#261 |
|
Staged for next release. Thanks. |
|
Thank you for merging this @mj1856, and no need to apologize! |
|
Sorry about that. The docs are correct, but the deprecation warning was overlooked. |
|
No need to apologize @ichernev! |
|
Merged in 59ba744 |
ichernev
added a commit
that referenced
this pull request
Mar 6, 2016
Fix usage suggestions for min and max
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The deprecation warnings for instance
minandmaxgive incorrect substitutions. Per the current documentationmoment().minandmoment.max()should be replaced bymoment.maxandmoment.minrespectively. We learned this the hard way.https://jsfiddle.net/s5ex3qh7/
(open the console to see the deprecation warning)