diff options
| author | Martin Trigaux <mat@odoo.com> | 2017-03-04 22:45:53 +0100 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2017-03-07 15:57:37 +0100 |
| commit | 76b724294aa21c83edd3409d4664e041dd70cd00 (patch) | |
| tree | 5f576a46bec40ef28d36be86d4a20ed2a432a73f /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | 8eb759dcff0c90e05fa2546615ed47a895e5f66a (diff) | |
[FIX] calendar: correct search in recurrent event
Add a 3 use cases with tests that were failing before.
datetime filters were not working correctly on stop filters
The `_get_recurrent_date_by_event` was only computing recurrency on the start
field of an event which can make a difference. A recurring event
start=2017-01-01 09:00:00; stop=2017-01-01 10:00:0
was not matched in a search ('stop', '>', '2017-01-01 09:30:00')
The filter != was not handled in the recurring use cases.
e.g. making the search 'start is set' in the web client is equal to
('start', '!=', False)
Searching with only a start filter matching recurring events but not the
first ("real") occurence, was returning no result if no stop filter was present.
start=2017-01-01 09:00:00; count=5
had no result in a search ('start', '>', '2017-01-02')
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
