Describe the bug
In IE, when the dayjs object is generated by Date object, the formatted string of milli seconds show '000' always.
Please see this JSFiddle.
(https://jsfiddle.net/7jrdo1bz/)

It seems be correct behavior when dayjs object is generated by unix milliseconds.
(like: dayjs(1575441029123))

Expected behavior
Show correct milli seconds.

Information

• Day.js Ver

parseISO v2 documentation currently states

The previous parse implementation was renamed to parseISO.

parse v2 documentation currently states

Old parse was renamed to toDate. Now parse is a new function which parses a string using a provided format.

I think considering the sentence is to divert people who have previously been using v1 parse to the correct v2 equivalent, it only

• I have marked all applicable categories:
  • exception-raising bug
  • [ x] visual output bug
  • documentation request (i.e. "X is missing from the documentation." If instead I want to ask "how to use X?" I understand [StackOverflow#tqdm] is more appropriate)
  • new feature request
• [ x] I have visited the [source website], and in particular
  read the [known iss

Thank you for your work on pickadate!

As far as I can tell, pickadate works nicely with jQuery's slim build; if that is in fact the case (and long-term intent), it might be worth mentioning that.

Hi,

the shift() method is nice and seems to work with localized time with some kind of "natural" semantic. However it leads to some results (related to differences between time points).

>>> t0 = arrow.now().shift(weeks=3)    # The day before the next DST fall transition

>>> t0
<Arrow [2019-10-26T16:33:24.883042+02:00]>

>>> t1 = t0.shift(days=1)

>>> t1
<Arrow [2019-10-27T16

Parsing token 'x' according to documentation it should parse to microseconds timestamp but it parses to milliseconds timestamp. Not sure what was intended here but there is a discrepancy.
code:
_TOKENS = ( ... "x": lambda dt: "{:d}".format(dt.int_timestamp * 1000 + dt.microsecond // 1000)

I personally don't like the format that toLocaleString() returns (24/10/2019 2:36:56).

It would be nice if there was an option to pass its options like dateStyle: 'long', timeStyle: 'short', etc.

e.g.

$.timeago.settings.LocaleFormat = {dateStyle: 'medium', timeStyle: 'short', hour12: true};
// $(this).attr("title", date.toLocaleString(undefined, $t.settings.LocaleFormat));
``

The description says:

A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.

But actually it provides a way to stub, not to mock.

I'd like an /Examples folder with some simple iOS apps showing how to use Time.

The first one that comes to mind is a basic iOS app using a UICollectionView to build a month calendar view.

USE_AUTOLOAD=0 is set if USE_SYSTEM_TZ_DB is true and USE_AUTOLOAD=1 otherwise. What is it for? I can't see anything that it is attached to. Is it to do with CURL?

Perhaps some documentation (in README or inline comments) on this and HAS_REMOTE_API would be useful?

It would be nice if we could pretty print a range. For instance :

"on April 1st between 10:45 and 11:45"
"between April 1st and April 3rd"
"between April 1st at 9:00 and April 3rd at 18:00"
"on April 1st at 10:45 for 1 hour"

Not sure what the API would be though.

Feature request: I nedd (my wife needs to be honest) additional functionality - editing appointments from customers page (i.e. click customer from list on the left, select appointment from the list and click edit button). For now editing appointment is possible from calendar view only. TIA.

add a min() and max() property that shortcuts generating a list of events if possible.
If the Python Object model had a __min__() and __max__() this would be easier, but a min and max method is still better.

How it would work:
If the instance has a _dtstart or _until return those values instead of iterating and expanding the entire set of data.

This would be a massive speedup.

The textual information does match with the screenshot mentioned in the page:
https://kamon.io/docs/latest/guides/installation/setting-up-the-agent/#in-a-nutshell
The test refers to kanela jar whereas the screenshot refers to aspectjweaver

While there are some issues/PRs (#243, #284, etc.) relating to wasm, there is no specific section in documentation properly detailing steps to use it with something like wasm-pack.

For now (v0.4.10), the following code fails to compile:

extern crate wasm_bindgen;

use wasm_bindgen::prelude::*;
use chrono::{NaiveDate};

#[wasm_bindgen]
pub struct Request {
    date: NaiveDat

In PR #188 we so aw, that users not familiar with the threeten/joda API consider our overloaded functions (e.g. Year.now0, Year.nowClock, ...) to be public API

It is important to us to change the threeten API as little as possible for JS, so we do not consider these public.

While we know that we cannot stop people from using the functions, we want to make it clear, that rather the ove