duckling_old

duckling_old copied to clipboard

PR mainly to fix the improper shifting of interval endpoints in the "inclusive" case. Currently breaks a corpus example -- fixing this requires some discussion. Related issue: #221.

almostimplemented

[EN] Intervals with differing grains

1

Example of issue: ``` duckling.core=> (pprint (parse :en$core "Today between 8:30 AM and 9 AM" [:time])) ({:dim :time, :body "Today between 8:30 AM and 9 AM", :value {:type "interval", :from...

almostimplemented

When people say "in two days" or "three days ago", they typically are referring to the whole day. Currently, `duckling.time.prod/duration-ago` and `/in-duration` (typically) change the grain to be one below...

almostimplemented

The NYSE market opens at 9:30 and closes at 4:00 on weekdays, however it closes for US holidays. It would be nice if Duckling were able to parse datetime phrases...

dyladan

Add a "context time"

5

This could be related to #90, but more "static". Now there's the "reference time", the time where the user lives in the present, so "today" is the day of the...

ibobo

Extend new language - Thai language. But there is some pattern to fix.

1

Following [issue#104:](https://github.com/wit-ai/duckling/issues/104) Signed-off-by: Pongsakorn Eiamrod [email protected]

Bongsakorn

adding italian new time entities

1

redbaron76

Checker functions should take a context and a token. They can check for the token value by applying the `:value` key. However, some checker fns reverse the context and token...

joachimdb

https://github.com/wit-ai/duckling/blob/master/src/duckling/core.clj#L36 The `classifiers` parameter is never used. It should be removed or given a purpose.

joachimdb

The `reference-time` cannot contain time zone information that is not a full hour (e.g. India is UTC+05:30). I guess it's caused by this check: ```clojure (integer? timezone) (time/time-zone-for-offset timezone) ```...

FraBle