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

I'd like to contribute to the documentation by adding some of the available options which are not currently documented on the site.

An example of that is the minuteIncrement config that I had dive into the documentation to find it myself. I'm sure a few people might have had a need for this but never found it.

Which repo do I need to fork to be able to contribute this to the documentation?

The doc on https://moment.github.io/luxon/docs/class/src/interval.js~Interval.html states that:

To convert the Interval into other representations, see toString, toISO, toISODate, toISOTime, toFormat, and toDuration.

However, the link to toFormat() goes to the DateTime documentation page (it took me a while to realize this), and that page says:

You may not want this. See toLocaleStr

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)

问题描述

作者是个菜鸟，请详细地描述问题，不要一句话带过（特别是将描述放在标题上的），根据情况贴上代码

处理 issue 是件很耗精力的事，请提交 issue 前考虑一下是否把问题说清楚了

产生环境

• **使用版本：-
• **引入方式：CDN | NPM
• **演示地址：-

提示错误信息

1. Invalid prop: custom validator check failed for prop "startDate".
2. Invalid prop: custom validator check failed for prop "endDate".
3. Invalid prop: custom validator check failed for prop "value".

代码区域

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?

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.

Steps to reproduce

iex> t1 = "2019-04-03T21:07:45Z" |> Timex.parse!("{ISO:Extended:Z}") |> Timex.to_datetime("Europe/Berlin")
#DateTime<2019-04-03 23:07:45+02:00 CEST Europe/Berlin>
iex> Timex.day(t1)
93
iex> t2 = "2019-04-03T22:07:45Z" |> Timex.parse!("{ISO:Extended:Z}") |> Timex.to_datetime("Europe/Berlin")
#DateTime<2019-04-04 00:07:45+02:00 CEST Europe/Berlin>
iex> Timex.

Versions

• vue: 2.6.10
• vue-datetime: 1.0.0-beta.10
• luxon: 1.19.3

Description:

Feature Request

I don't see any template slot to be used to replace with default input field of datepicker.
It would be a good idea to provide a slot so we can provide ours on html for the date input field.

_What I really just want is an option to put a calendar icon to the right of date inpu

Describe the bug
Given:

reference_date = datetime.datetime.now()
timex_date = Timex.from_date(datetime.datetime.now())
print(f"{timex_date.timex_value()} : {timex_date.to_natural_language(reference_date)}")

Outputs:

2019-11-12 : 12nd November 2019

Expected behavior
The .Net version returns:

2019-11-12 : today

**Platform (please complete th

1999 is disabled despite the date range:

Prev page, 1999 is enabled but 1989 is disabled. It seems every first and last year is disabled without any reason:

dateutils.dseq 2018-03-05 2018-05-15 -f '%F %a %c %u' | dateutils.dgrep '%c=04'

Expected output:

2018-03-22 Thu 04 04
2018-03-23 Fri 04 05
2018-03-24 Sat 04 06
2018-03-25 Sun 04 07
2018-03-26 Mon 04 01
2018-03-27 Tue 04 02
2018-03-28 Wed 04 03
2018-04-22 Sun 04 07
2018-04-23 Mon 04 01
2018-04-24 Tue 04 02
2018-04-25 Wed 04 03
2018-04-26 Thu 04 04
2018-04-27 Fri 04 05
20