[17.0][MIG] web_refresher: Migration to 17.0#2669
Conversation
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: web-16.0/web-16.0-web_refresher Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_refresher/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: web-16.0/web-16.0-web_refresher Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_refresher/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: web-16.0/web-16.0-web_refresher Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_refresher/
Currently translated at 100.0% (2 of 2 strings) Translation: web-16.0/web-16.0-web_refresher Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_refresher/hr/
Currently translated at 50.0% (1 of 2 strings) Translation: web-16.0/web-16.0-web_refresher Translate-URL: https://translation.odoo-community.org/projects/web-16-0/web-16-0-web_refresher/fr/
|
/ocabot migration web_refresher |
|
Tested on runbot and working. question: Is there a reason to put the button on the center instead of next to the pager as always? |
Hi, there were a few reasons for that, in previous versions, page refresh was not available on all views where it was most often needed, in the current version I attach this in not only pager, which allows you to get this functionality almost everywhere. In the image of odoo 15, as you can see, the update functionality is not available, so placing it in the search component solves this problem |
If someone else can confirm that this position is strange or inconvenient, I'll move this to the pager as it was before, but I'm not sure that this functionality will be available on reports |
now I'm working on the preliminary look, it looks like everything could be fine |
0a1c79f to
68c5beb
Compare
|
|
||
| async onClickRefresh() { | ||
| await this.refresh(); | ||
| this.notification.add(_t("Refreshed"), { |
There was a problem hiding this comment.
No very convinced with this :) Is it really needed?
There was a problem hiding this comment.
No very convinced with this :) Is it really needed?
Are you talking about this.notification.add or the entire component?
There was a problem hiding this comment.
Yes, just the notification of the refresh :)
There was a problem hiding this comment.
this is not necessary, but I noticed in my experience that if you do not display anything, it is not immediately clear whether the click has worked, in a situation where there were no new changes to update
There was a problem hiding this comment.
If you think it's unnecessary or distracting, I can remove it
There was a problem hiding this comment.
Maybe a shorter notification close timeout would be less anoying
There was a problem hiding this comment.
ok, I'll think about a simplified version of the notification, as a last resort I'll just remove it.
I'll deal with it later.
Any other comments on other points?
68c5beb to
8ec3058
Compare
8ec3058 to
21765c4
Compare
jcdrubay
left a comment
There was a problem hiding this comment.
Test on runboat, it works very nicely. Nice :)
|
This PR looks fantastic, let's merge it! |
|
This PR has the |
|
Congratulations, your PR was merged at 0958651. Thanks a lot for contributing to OCA. ❤️ |



No description provided.