New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

natural language parser can't parse 100 as value #1226

Closed
fadanner opened this Issue Jun 8, 2015 · 2 comments

Comments

Projects
None yet
4 participants
@fadanner

fadanner commented Jun 8, 2015

Using the natural language parser keywords containing "100" aren't parsed correctly.
This is in rest-api and in the web-interface (even in the Preview text)

Example:

  • last 99 days : Preview:2015-03-01 09:24:41 to 2015-06-08 09:24:41 correct
  • last 100 days: Preview:2015-06-08 10:00:00 to 2015-06-08 09:26:35 bug
  • last 101 days: Preview:2015-02-27 09:26:49 to 2015-06-08 09:26:49 correct

Same with 999, 1000 and 1001 days. or with minutes as keyword

@joschi joschi added the bug label Jun 8, 2015

@joschi joschi self-assigned this Jun 8, 2015

@joschi joschi added this to the 1.1.2 milestone Jun 8, 2015

@kroepke kroepke closed this Jun 9, 2015

@kroepke

This comment has been minimized.

Member

kroepke commented Jun 9, 2015

closed the wrong one…

@kroepke kroepke reopened this Jun 9, 2015

@bernd

This comment has been minimized.

Member

bernd commented Jun 10, 2015

Isn't this fixed by #1227?

@joschi joschi closed this in f3ab9e2 Jun 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment