[18.0][MIG] date_range #956

BertVGroenendael · 2024-10-16T10:28:27Z

No description provided.

* [ADD] Basic structure for the new date range module * [IMP] Add a basic description into the README * [IMP] Basic implementation * [IMP] First working implementation * [IMP] Improve datamodel * [ADD] Add basic tests for date.range * [PEP8] * [PYLINT] * [DEL] Remove unused code * [IMP] Remove unsused dependencies into the JS * [IMP] Better operator label for date range * [DEL] Remove unused file * [IMP] Better user experience by showing the select input only once empty * [FIX]Try to fix tests that fails only on travis by adding an explicit cast on the daterange methods parameters * [FIX]Try to fix tests that fails only on travis by adding an explicit cast on the daterange methods parameters * [FIX]Try to fix tests that fails only on travis by using postgresql 9.4 * [FIX]Try with postgresql 9.2 since the daterange method has appeared in 9.2 * [IMP] Add a limitation into the module description to warm about the minimal version of postgresql to use * [IMP]Add multi-company rules * [IMP]Remove unused files * [FIX] Add missing brackets into JS * [FIX] Overlap detection when company_id is False * [IMP] Add default order for date.range * [IMP] Add date range generator * [FIX] OE compatibility * [FIX] Travis * [IMP] Code cleanup and improves test coverage * [FIX] Add missing dependency on 'web' * [PYLINT] remove unused import * [FIX] Add missing copyright * [FIX] Limits are included into the range * [IMP][date_range] Security * [IMP] Improve module description * [IMP] Spelling

* Improve 'name' for generator wizard ir.rule should be active by default * Don't auto-add '-' after prefix when generating date ranges via wizard * code fine tuning suggested by Sylvain Garancher

If any module adds a required field on company, module fails. Executing it on post_install, there's no problem.

Pylint-odoo is not able to detect properly whitelisted odoo's dependencies if an isort configuration file is present into the directory. Therefore the check fails by complaining that the dateutil dependecy is not declared into the manifest. A fix could have been to declare the dependency into the manifest . Unfortunately, in this case, a warning will be issued by runbot complaining that the python external dependency dateutil should be replaced by it's PyPI package name. Unfortunalely, if we put the Pypi package name into the external dependencies, pylint fails again since it's not able to play with PyPI distribution names. The workaround is to temporarily disable this check into pylint. I every case, all the pre-commit files will be reset once pylint will be fixed

We can't assign an empty recordset in a computed writable for a required field for triggering DB fault, as previously this we get an akward error no in current ORM status: ERROR: operator does not exist: integer = boolean LINE 12: AND dt.type_id=false; ^ HINT: No operator matches the given name and argument types. You might need to add explicit type casts. so let's simply trigger in this case the check of the company consistency, which is legit and the final expected result. I have added an extra test for testing the company consistency the other way around.

Because ev.target.value is a string and the range ids are integers, comparison was always false, so the first range values were always used.

thienvh332

Hi @BertVGroenendael ,
I did a UI test and found the same issue as issue #821. You can pick this commit from v14 to resolve it.

date_range/models/date_range_search_mixin.py

ivantodorovich · 2024-11-04T12:52:34Z