tsm-odoo
cdc35aed74
This PR adds the `add_guest_to_context` decorator in order to provide a generic way to extract the guest from a request. It will be used to unified guest extraction from cookie/param based on its provenance (external livechat/public page). This is better than the `pre_dispatch` method since it can be applied to specific routes instead of adding this logic to every request. part of task-3332628 closes odoo/odoo#130052 Signed-off-by: Matthieu Stockbauer (tsm) <tsm@odoo.com>
21 lines
835 B
Python
21 lines
835 B
Python
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from werkzeug.exceptions import NotFound
|
|
|
|
from odoo import http
|
|
from odoo.http import request
|
|
from odoo.addons.mail.models.discuss.mail_guest import add_guest_to_context
|
|
|
|
|
|
class GuestController(http.Controller):
|
|
@http.route("/mail/guest/update_name", methods=["POST"], type="json", auth="public")
|
|
@add_guest_to_context
|
|
def mail_guest_update_name(self, guest_id, name):
|
|
guest = request.env["mail.guest"]._get_guest_from_context()
|
|
guest_to_rename_sudo = guest.env["mail.guest"].browse(guest_id).sudo().exists()
|
|
if not guest_to_rename_sudo:
|
|
raise NotFound()
|
|
if guest_to_rename_sudo != guest and not request.env.user._is_admin():
|
|
raise NotFound()
|
|
guest_to_rename_sudo._update_name(name)
|