[16.0][MIG] web_field_tooltip: Migration to 16.0 #2783
Conversation
…ip on list views. One tooltip per field and do not handle user specific tooltips
…tip from the helper, splitted resources into multiple files
benwillig
force-pushed
the
16.0-mig-web_field_tooltip
branch
2 times, most recently
from
ee2faec to
364f7f2
Compare
benwillig
force-pushed
the
16.0-mig-web_field_tooltip
branch
from
364f7f2 to
e729006
Compare
| Contributors | ||
| ~~~~~~~~~~~~ | ||
|
|
||
| * Benoit Aimont <[email protected]> (https://www.acsone.eu/) |
There was a problem hiding this comment.
And Benjamin Willig, innit?
| @@ -0,0 +1 @@ | |||
| * Benoit Aimont <[email protected]> (https://www.acsone.eu/) | |||
There was a problem hiding this comment.
And Benjamin Willig, innit?
| @@ -0,0 +1 @@ | |||
| * Find a way to update form views after tooltips update without refreshing manually | |||
There was a problem hiding this comment.
yes but I dont think we should do something about it.
|
This PR has the |
|
/ocabot merge nobump |
|
What a great day to merge this nice PR. Let's do it! |
|
Congratulations, your PR was merged at 59c5e00. Thanks a lot for contributing to OCA. ❤️ |
| name = fields.Char( | ||
| compute="_compute_name", | ||
| readonly=True, | ||
| ) |
There was a problem hiding this comment.
hi @benwillig, I created this PR to follow up your change to re-declaring the field_name (since the field_name below was not deleted, causing your store=True change to seem to be overwritten). but I wonder why this change is made because when the field_name is not stored, the module still functions properly
No description provided.