Börje Karlsson

See discussion in #2843.

Currently the recognizers don't properly represent "approximatedly/about/around" as the approx modifier consistently across all number sub types. See example in KO in #2835. This can be an important semantics signal...

In some situations it seems code resource regeneration from YAML itself fails, but the build continues with the older code resources. Any failure in code generation from YAML, in any...

[JavaScript] lerna/ava versions old versions causing dependency update issues

1

JavaScript build system needs to be updated. Current versions of lerna/ava block upgrading some code dependencies.

[DE DateTimeV2] Inconsistent behaviour recognizing complex entities including “frühmorgens”

1

* “frühmorgens” not recognized correctly if preceded by Holiday and followed by time Ex: "an Weihnachten frühmorgens um 8:00" * Time not recognized correctly if preceded by both day-of-week and...

It seems if users don't have the hooks setup, they can still create PRs and lint issues are not captured in build. This leads to issues where future pushes from...

For example, in input "a kilo of salt", "a kilo" should be tagged as entity. Not just the unit itself.

Input like "Silvester spätabends um 8:00" currently returns three separate entities. It should at least merge time-range and time, or ideally, merge all three into a single entitiy.

[* DateTimeV2] Refactor Holiday resolution logic to improve defintion re-use across cultures

1

Move common holiday definitions and concrete dates to common resources BaseDateTime.yaml and BaseHolidayParserConfiguration, if the same for all supported cultures. International/standard holidays could be moved to the Base resources/parsers and...

[EN|DE DateTimeV2] Holiday + time of day not being merged

1

Currently entities are returned separately in cases of holiday + time-of-day. If possible, the output should be merged into a single entitiy. Examples: - New Year's Eve at night -...