[IMP] avoid base_sparse_field --load#47
Merged
Merged
Conversation
`base_sparse_field` patches odoo fields in order to be able to use `fields.Serialized`. To "pay" this shortcut you have to load it at server load which makes harder to test it with external tools (ie: pytest) and disorient first users as they always miss this step. Now we load the field straight from the module: easy, neat, works.
Contributor
Author
|
NOTE: runbot is yellow for: |
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
3 participants
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.
base_sparse_fieldpatches odoo fieldsin order to be able to use
fields.Serialized.To "pay" this shortcut you have to load it at server load
which makes harder to test it with external tools (ie: pytest)
and disorient first users as they always miss this step.
Now we load the field straight from the module: easy, neat, works.