Repository navigation
Conversation
Currently translated at 47.8% (11 of 23 strings) Translation: hr-13.0/hr-13.0-hr_contract_rate Translate-URL: https://translation.odoo-community.org/projects/hr-13-0/hr-13-0-hr_contract_rate/fr_FR/
Currently translated at 100.0% (26 of 26 strings) Translation: hr-14.0/hr-14.0-hr_contract_rate Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_contract_rate/es_AR/
Currently translated at 100.0% (26 of 26 strings) Translation: hr-14.0/hr-14.0-hr_contract_rate Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_contract_rate/it/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-14.0/hr-14.0-hr_contract_rate Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_contract_rate/
Currently translated at 15.3% (4 of 26 strings) Translation: hr-14.0/hr-14.0-hr_contract_rate Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_contract_rate/es/
Currently translated at 100.0% (26 of 26 strings) Translation: hr-14.0/hr-14.0-hr_contract_rate Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_contract_rate/es/
Ported from 14.0, the last series the module exists in. - Install hooks take ``env``. ``pre_init_hook`` only seeds contracts that have no amount yet; ``post_init_hook`` is gone: the ORM computes the new stored fields of the existing contracts by itself, and calling ``_compute_wage()`` outside of a compute went through the inverse of ``wage``. - The contract form of 18.0 lays the wage out differently: amount and period now replace the wage box on one line, sized by a small stylesheet. - ``AMOUNT_PERIOD_SELECTION`` is exported so other models can share the keys of ``amount_period``. - Tests cover every period, the inverse of ``wage`` and the form view.
… written The fields computed together with ``wage`` are protected from recomputation while it is being written, so writing a wage on an hourly, daily or weekly contract stored the monthly amount but left ``approximate_wage`` and ``is_wage_accurate`` describing the old rate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migration of
hr_contract_rateto 18.0 from 14.0 (it was not ported to 15.0-17.0, and #1401 for 16.0 was closed).Standard migration, module history preserved. Main changes:
env.post_init_hookremoved, the ORM already computes the stored fields on install.track_visibility->tracking.AMOUNT_PERIOD_SELECTIONexported so other modules can reuse the keys.[FIX]commit: writingwageon an hourly/daily/weekly contract leftapproximate_wageoutdated.I'm using it in production.
@OCA/hr-maintainers