tsm-odoo
850367e954
The createChatterContainer helper was used during tests to mount a chatter container and test it. However, this approach is not very realistic and blocks some waiting PRs. In order to get closer from the reality, let's mount a webClient and open a form view containing a chatter. closes odoo/odoo#94175 Related: odoo/enterprise#28684 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
39 lines
1.2 KiB
JavaScript
39 lines
1.2 KiB
JavaScript
/** @odoo-module **/
|
|
|
|
import { registry } from '@web/core/registry';
|
|
|
|
const viewArchsRegistry = registry.category('mail.view.archs');
|
|
const activityArchsRegistry = viewArchsRegistry.category('activity');
|
|
const formArchsRegistry = viewArchsRegistry.category('form');
|
|
const kanbanArchsRegistry = viewArchsRegistry.category('kanban');
|
|
const listArchsRegistry = viewArchsRegistry.category('list');
|
|
const searchArchsRegistry = viewArchsRegistry.category('search');
|
|
|
|
activityArchsRegistry.add('default', '<activity><templates></templates></activity>');
|
|
formArchsRegistry.add('default', '<form/>');
|
|
kanbanArchsRegistry.add('default', '<kanban><templates></templates>');
|
|
listArchsRegistry.add('default', '<tree/>');
|
|
searchArchsRegistry.add('default', '<search/>');
|
|
|
|
formArchsRegistry.add(
|
|
'res.partner',
|
|
`<form>
|
|
<sheet>
|
|
<field name="name"/>
|
|
</sheet>
|
|
<div class="oe_chatter">
|
|
<field name="activity_ids"/>
|
|
<field name="message_follower_ids"/>
|
|
<field name="message_ids"/>
|
|
</div>
|
|
</form>`
|
|
);
|
|
formArchsRegistry.add(
|
|
'res.fake',
|
|
`<form>
|
|
<div class="oe_chatter">
|
|
<field name="message_ids"/>
|
|
</div>
|
|
</form>`
|
|
);
|