Adrien Ball

# Parsing Error Parsing "from 8am on august 3rd to 10pm on november 3rd 2019" results in a wrong resolution for the `from` date. The resolution is correct when trying...

Forwarding the issue https://github.com/snipsco/snips-nlu/issues/833. > Hi, > > Depending on how a question is asked, the timeframe identified for winter varies: > > * "in winter": > > ``` >...

# Parsing Error This issue was initially raised here: https://github.com/snipsco/snips-nlu/issues/677 ## Version `0.17.5` ## Language `en` ## Parser input `Q1 2018` ## Parser output ``` Integer(IntegerOutput(2018)) ``` ## Parser expected...

cf this issue: https://github.com/snipsco/snips-nlu/issues/678

2K interpreted as datetime

2

# Parsing Error Rustling should not interpret values like `"2K"` as datetime. ## Version `0.17.5` ## Language `en` ## Parser input `cargo run -- --lang en parse "2K" -k Time`...

Rustling uses 12h-clock in country with 24h-clock

1

cf --> https://forum.snips.ai/t/nlu-uses-12h-clock-in-country-with-24h-clock/598

**Description** This PR adds a new (optional) `resolved_value_id` property in both the `EntityValue` and `ParsedValue` structs. This allows to associate an optional id to resolved values.