-
-
Notifications
You must be signed in to change notification settings - Fork 615
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
[16.0][MIG] mail_tracking: Migration to 16.0 #1216
[16.0][MIG] mail_tracking: Migration to 16.0 #1216
Conversation
5942941
to
13154c4
Compare
Hello @luisg123v, could you review this, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some serious issue when trying to test it functionally:
- Whenever a enter a record I get an error when it tries to load the failed messages tracker:
- The mail message filter isn't injected into the filter menu:
Also, if you took changes from the other PR is good to respect the contributor attribution in a separate commit |
9f7106f
to
d1a3359
Compare
Hello @chienandalu, thank you for testing, the issues you found should now be solved, could you check again, please? As for this comment:
I added a new commit as you suggested, but including Co-authorship and referencing the original PR, please let me know if there is a better/more respectful way of doing this, as I was not able to find a similar case in the guidelines, thanks again! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @payen000 :) That can be a way to attribute changes, yes :) (normally I try to cherry-pick and adapt, so I keep the original commit as similar as possible, but is ok)
Functionally I still see some issues:
- Clicking on the tracking status icon doesn't show up the trackings dialog.
- The failed messages review doesn't show up in the record thread either
33c61ff
to
caf2c08
Compare
6500e9c
to
1d3b076
Compare
Hello again @chienandalu, thank you for the tips, I appreciate it! I've updated the code, you should be able to see the failed messages and the tracking action now, could you check again, please? |
Hello @chienandalu, I've updated the code so that the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like your re-rendering the whole window after each action with the failed messages . Can't you use owl reactivity?
c2faec5
to
3915290
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Superb work! I made a succesful functional tour and a final code review
Just two final tweaks 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put yourself in the contributors list 😄 👍
mail_tracking/controllers/discuss.py
Outdated
|
||
class MailTrackingDiscussController(DiscussController): | ||
@http.route() | ||
def mail_init_messaging(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This method has a different signature (https://github.com/odoo/odoo/blob/913c8678cba0741e99610b1174ba6c42ef0c21a6/addons/mail/controllers/discuss.py#L194)
def mail_init_messaging(self): | |
def mail_init_messaging(self, **kwargs): |
632dc0c
to
504a304
Compare
Hello @chienandalu, Thank you for reviewing and testing this far, and of course, for your words of encouragement! I've added your suggested changes, could you check please? Also, I converted the 'message ids list' inside Thanks again! |
Oh, after the last changes:
|
504a304
to
1205086
Compare
Sorry @chienandalu, it seems I forgot to reset the runbot after my own tests, that's why most of the records were not visible as failed, after resetting the runbot the failed messages were visible again :) I've done one last push to re-render the "Retry" and "Set as reviewed" options properly from the Inbox/History/Starred mailboxes, could you check please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're ready 😄 👍
Thanks!
Thank you @chienandalu! |
Hello @luisg123v, could you review this, please? |
The following changes were implemented: 1 - Added Failed Message component and related components to reuse the Message component when rendering failed messages. This allows us to dispose of the messagefailed JS model altogether, since failed messages are now just regular messages that were marked as failed. 2 - Added Owl reactivity to failed message actions so that browser does not have to be reloaded each time a message is marked as reviewed or resent. 3 - Fixed 'Retry' and 'Set as reviewed' flows for failed messages. 4 - Fixed `Failed sent messages` filter on models by overriding `get_view` instead of `_fields_view_get` 5 - Refactored folder structure to more closely resemble the `mail` module's folder structure. 6 - Refactored module to utilize `Command` as a means to create, write, etc. instead of `[0, ...]`, `[4, ...]`. 7 - Fixed and added unit tests. 8 - Removed dead/unused code from `v15`.
1205086
to
ef73e2d
Compare
Hello @luisg123v, I've applied your suggestions, could you check please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
/ocabot merge nobump |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at a324624. Thanks a lot for contributing to OCA. ❤️ |
Redo of PR #1191; this PR is opened due to inactivity of #1091 (from which the
MessagingInitializer._init
fix was taken).