tablecloth.time.api.converters — org.scicloj/tablecloth.time 1.00-alpha-3

->days clj

(->days datetime)

->every clj

(->every interval chrono-unit)

(->every interval chrono-unit datetime)

->hours clj

(->hours datetime)

->instant clj

(->instant datetime)

Convert any datetime to an instant.

->local-date clj

(->local-date datetime)

Convert any datetime to a local date.

->local-date-time clj

(->local-date-time datetime)

Convert any datetime to a local datetime.

->minutes clj

(->minutes datetime)

->months-end clj

(->months-end datetime)

->quarters-end clj

(->quarters-end datetime)

->seconds clj

(->seconds datetime)

->weeks-end clj

(->weeks-end datetime)

->years-end clj

(->years-end datetime)

anytime->milliseconds clj

(anytime->milliseconds str-or-datetime)

(anytime->milliseconds str-or-datetime timezone)

Converts any time unit type to milliseconds.

convert-to clj

(convert-to datetime datetime-type)

Convert time to different type as specified by datetime-type.

down-to-nearest clj

(down-to-nearest interval chrono-unit)

(down-to-nearest interval chrono-unit datetime)

milliseconds->anytime clj

(milliseconds->anytime millis datetime-type)

(milliseconds->anytime millis datetime-type timezone)

Convert milliseconds to any time unit as specified by datetime-type.

milliseconds-in clj

(milliseconds-in chrono-unit)

milliseconds-since-epoch->year clj

(milliseconds-since-epoch->year millis)

(milliseconds-since-epoch->year millis timezone)

string->time clj

(string->time str)

Given an identifiable time, returns the correct datetime object. Optionally, you can specify a target type to also convert to a different type in one step.

TODO: How do we define what an 'identifiable' string means?

year->local-date clj

(year->local-date year)

year->milliseconds-since-epoch clj

(year->milliseconds-since-epoch year)