Skip to content
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

Calculate keyword from and to values on the fly #2335

Merged
merged 1 commit into from Jun 9, 2016
Merged

Calculate keyword from and to values on the fly #2335

merged 1 commit into from Jun 9, 2016

Conversation

edmundoa
Copy link
Contributor

@edmundoa edmundoa commented Jun 6, 2016

Keyword time ranges may be in memory for a while, and the range they represent may change over that time. Currently, they are also inconsistent with the way relative ranges work, which are calculated when getFrom() and getTo() are called. These changes avoid those two problems by calculating the keyword from and to values when the methods are called.

The changes should be merged into master as well.

Fixes #2301.

Keyword time ranges may be in memory for a while, and the range they
represent may change over that time. Currently, they are also inconsistent
with the way relative ranges work, which are calculated when `getFrom` and
`getTo` are called.

These changes avoid those two problems by calculating the keyword from and
to values when the methods are called.

Fixes #2301
@edmundoa edmundoa added this to the 2.0.3 milestone Jun 6, 2016
@edmundoa
Copy link
Contributor Author

edmundoa commented Jun 6, 2016

By the way, to test it I was using a widget created using last five minutes as keyword search.

@joschi joschi self-assigned this Jun 9, 2016
@joschi
Copy link
Contributor

joschi commented Jun 9, 2016

LGTM. 👍

@joschi joschi merged commit 3c4550a into 2.0 Jun 9, 2016
@joschi joschi deleted the issue-2301 branch June 9, 2016 15:03
joschi pushed a commit that referenced this pull request Jun 9, 2016
Keyword time ranges may be in memory for a while, and the range they
represent may change over that time. Currently, they are also inconsistent
with the way relative ranges work, which are calculated when `getFrom` and
`getTo` are called.

These changes avoid those two problems by calculating the keyword from and
to values when the methods are called.

Fixes #2301
(cherry picked from commit 3c4550a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants