forked from OCA/server-tools
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Syncing from upstream OCA/server-tools (18.0) #1649
Merged
Merged
Conversation
This file contains 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
… 13.0) to OCA/server-tools Based on commit 746b7acbd90d62f9ffe6ee17472a1a3533e36597 (Fri Nov 6 17:18:47 2020 +0100) Co-authored-by: Stefan Rijnhart <[email protected]>
… make the module installable, add readme folders
…y to select some modules, and improve filters, regarding test module with startswith and endswith pattern
Co-authored-by: Stefan Rijnhart <[email protected]>
… (replaced by logger), apply pre-commit rules
…using upgrade-path
[IMP] guess upgrade_path, if config is not set, and openupgrade_scripts is available
Co-authored-by: David Beal <[email protected]>
Given that the records need to be managed in the modules that own them rather in the modules that override them, and that we also have the noupdate data xml for every module, then we left out the lines that where indicating the override of records.
Includes minor fixes.
Just in case.
Add new item in the roadmap section for the next migration of the module in V16
…ted fields Odoo 14 introduced the widescale usage of computed fields with readonly=False. In that case, the compute method functions as a default that can also be used to compute a value some time *after* the initial creation of the record. In the OpenUpgrade analysis files, these fields would be misrepresented as computed fields rather than fields with a default function. This change fixes that.
Check "module" is in context when patching init_models
The colspan property of some UI elements were not correctly adjusted to the v16 sytem. This commits fixes it.
Odoo has deprecated such modules with a pre-hook raising an error, so they are not installable anymore. This way, we avoid them to be included in the Install Modules Wizard.
This allows to circumvent Odoo's complaint of 'openupgrade_scripts/scripts/' is not a valid upgrade directory when there are no analysis files present yet.
…ed RST file to allow for very long module name
as odoo core was changed in a way that optimized away our logging
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: server-tools-18.0/server-tools-18.0-upgrade_analysis Translate-URL: https://translation.odoo-community.org/projects/server-tools-18-0/server-tools-18-0-upgrade_analysis/
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.
bt_gitbot