[10.0] [MIG] base custom info#1115
Conversation
# Conflicts: # base_custom_info/__manifest__.py
* Now you can define properties types, and access rules are inherited from the model/record linked to the custom info record. * Simplified version of computed value. * Implement for res.partner. * Add tests and fix bugs discovered in the meantime. * Allow to disable partner custom info tab, and custom info menu. * All of it can be set within general settings. * Now, by default, this module does not display custom info for partners unless in demo mode. Better fit for a base module. * You can disable the top menu entry too if it disturbs you, or enable it for everybody. * Give a special form when editing in partner custom info tab. * Sortable properties. * Sort values at onchange time. * Improve performance in onchange. * Split in several model files. # Conflicts: # base_custom_info/__manifest__.py # base_custom_info/i18n/es.po
- Select an option with an additional template and get it filled on the owner. - Drop support for onchange, too many bugs to workaround. - Improve demo data. - Improve tests. - Almost cool material icon, this is an app now! - Fun pics. # Conflicts: # base_custom_info/__manifest__.py
# Conflicts: # base_custom_info/i18n/es.po
|
Please check Travis status |
|
Wouldn't it be better to leave all as LGPL for an addon such as this one? 🤔 |
|
Module is LGPL already, but I think we missed to change manifest key. |
|
Hi all, in this example of readme: https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0 |
|
I think so |
9486f79 to
b6a9175
Compare
|
Hi all, switch back to LGPL as v9. |
|
@yajo : I'm working this module for v11. |
|
@fanha99 I remember problems with onchange implementation. It was supposedly fixed in Odoo itself, although in the mean time we managed to get a workaround. Read from #492 (comment) onwards, all I can say to you must be there. OTOH, it's easier to discuss on the v11 PR, with runbot & so on. Let's focus on finishing this one and then you can open the v11 and we can talk on that if you like. |
leemannd
left a comment
There was a problem hiding this comment.
A few nitpicking, but averall work looks good to me.
Thanks!
|
@TelmoSenseFly Not sure it can be merged now. We have internal testing coming tomorrow. |
|
@leemannd No worries. It will be fine to wait for tomorrow. |
|
hi @leemannd , @TelmoSenseFly, could you please review again? thx. |
|
Could this be merged? |
|
I think this doesn't contain latest changes in v9. |
|
OK. Since I use this module along with other that depend on it, should I try to migrate it after a rebase? |
|
OK |
could you please tell me which changes is it? |
|
@fanha99 sorry, they are there. Please squash your 2 migration commits and I'll merge. |
c71d9ab to
b51d348
Compare
|
@pedrobaeza : done |
Syncing from upstream OCA/server-tools (12.0)
almost change nothing from 9.0