Nicolas Bayet
4813f42997
Jinja as a templating engine was problematic in differents respect:
- introduce external dependency to Odoo (less controll)
- add another templating mechanism in the stack
- specific feature in qweb cannot be reused
- difficulty in rendering easily editable templates
- more knowledge required with no betterment
By replacing jinja with qweb we can now build tools to edit a qweb
that will work with the previously jinja encoded document
(essentially `mail.template` records).
There is a catch however. Some email fields (eg. email_to) used jinja
syntax for rendering dynamic variables (ie. ${object.something} and
${object.something_that_should_not_be_escaped | safe}).
We still want user to use dynamic variables for some char fields (eg.
subject, from, to, ...). We made a new rendering engine called
"inline_template" that will render an expression enclosed by `{{` and
`}}`.
To be able to edit the templates from the backend interface, a
plugin to the Odoo editor has been made for seamlessly edit the
document.
This qweb plugin includes:
- make dynamic variables (eg. `<t t-out="variable"/>`) not editable
(for preventing the user to shoot himself in the foot)
- group and hide related logical branching (ie. t-if, t-elif, and t-else)
in order to see only one at once
- a floating select input to switch visibility of a particular logical
branching
Task-27033
X-original-commit: odoo/odoo@68182baff4
Part-of: odoo/odoo#77377
53 lines
2.2 KiB
Python
53 lines
2.2 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from odoo.addons.test_mail.tests.common import TestMailCommon, TestRecipients
|
|
from odoo.tests import tagged
|
|
from odoo.tests.common import users
|
|
|
|
|
|
@tagged('mail_composer_mixin')
|
|
class TestMailComposerMixin(TestMailCommon, TestRecipients):
|
|
|
|
@classmethod
|
|
def setUpClass(cls):
|
|
super(TestMailComposerMixin, cls).setUpClass()
|
|
cls._init_mail_gateway()
|
|
|
|
cls.mail_template = cls.env['mail.template'].create({
|
|
'subject': 'Subject for {{ object.name }}',
|
|
'body_html': '<p>Body for <t t-out="object.name"/></p>',
|
|
})
|
|
|
|
@users("employee")
|
|
def test_content_sync(self):
|
|
record = self.env['mail.test.composer.mixin'].create({
|
|
'name': 'Invite',
|
|
'template_id': self.mail_template.id,
|
|
})
|
|
self.assertEqual(record.subject, self.mail_template.subject)
|
|
self.assertEqual(record.body, self.mail_template.body_html)
|
|
|
|
subject = record._render_field('subject', record.ids)[record.id]
|
|
self.assertEqual(subject, 'Subject for %s' % record.name)
|
|
body = record._render_field('body', record.ids)[record.id]
|
|
self.assertEqual(body, '<p>Body for %s</p>' % record.name)
|
|
|
|
@users("employee")
|
|
def test_rendering(self):
|
|
record = self.env['mail.test.composer.mixin'].create({
|
|
'name': 'Invite',
|
|
'subject': 'Subject for {{ object.name }}',
|
|
'body': '<p>Content from <t t-out="user.name"/></p>',
|
|
'description': '<p>Description for <t t-esc="object.name"/></p>',
|
|
})
|
|
self.assertEqual(record.subject, 'Subject for {{ object.name }}')
|
|
self.assertEqual(record.body, '<p>Content from <t t-out="user.name"/></p>')
|
|
|
|
subject = record._render_field('subject', record.ids)[record.id]
|
|
self.assertEqual(subject, 'Subject for %s' % record.name)
|
|
body = record._render_field('body', record.ids)[record.id]
|
|
self.assertEqual(body, '<p>Content from %s</p>' % self.env.user.name)
|
|
description = record._render_field('description', record.ids)[record.id]
|
|
self.assertEqual(description, '<p>Description for Invite</p>')
|