Monday, December 9, 2019
4 changes · master
Enhancements to existing features
This update gives major configuration sections clear internal names across many Odoo apps. It makes future customizations and extensions safer and easier to maintain, without changing how users interact with the settings screens.
Original PR description
Description of the issue/feature this PR addresses: Since all containers within a configuration view have the same class 'row mt16 o_settings_container' it doesn't allow for very clean/easy xpath expressions. By setting a name on evey major container we can do cleaner and safer xpath expressions that don't need any index or sub-xpaths.
Follow-up of https://github.com/odoo/odoo/pull/39613
Current behavior before PR: If you'd like to xpath into the purchase configuration view and and insert after the last element you'd have to create ugly xpaths with indexes. Something like `<xpath expr="//div[hasclass('o_settings_container'][3]" position="after"></xpath>`
Desired behavior after PR is merged: After this change you can do a clean and safer xpath expression like `<xpath expr="//div[@name='purchase_setting_container']" position="after"></xpath>`
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prCSV files used by Odoo can now include comment rows that start with #, making large manually maintained files easier to organize and update. This is mainly an internal developer convenience and should not affect normal business workflows, except that real data rows should not begin with #.
Original PR description
Certain manually-maintained csv files contain lots of data, sometimes it's hard to keep track of this data in an organized fashion and thus updating these files can become quite tedious. To make it easier for developers, we now allow the usage of comments in CSV files, since comments are not defined in the CSV spec, we arbitrarily decide that any row starting with # is a comment and will therefore be discarded before the parsing of the csv data. Note that this means that any actual data should not begin with #, if this turns out to be a problem, the algorithm may be replaced by a more robust one. Task-ID: 2127354 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Planning shifts can now select any task before a project is chosen, and the project will automatically align with the selected task. This reduces confusing restrictions and prevents accidental changes to a task's project when mismatched planning details are selected.
Original PR description
* existing static domain was almost exactly what we wanted: the only
issue was that if no project was selected (yet) we'd only allow
selecting tasks not linked to a project, whereas the dynamic domain
would allow selecting any task period (with an other onchange
updating the project to match the task)
* also simplify the task onchange:
- always set the project to the task's project
- if we somehow manage to select a project and a task which don't
match, don't go and move the task from one project to the other,
that doesn't seem very sane
Task 2115472The IoT app now includes sample IoT Boxes and connected devices for demonstration and testing. This makes it easier for users and teams to explore IoT workflows without manually creating example hardware records.
Original PR description
Add demo data for IoT Boxes and devices TaskID: 2092615