[IMP] web,*: properly define env in the frontend

*bus,mail

This commit extracts the common basis of the env to use both in
the frontend and the backend. The public env now contains most of
the features that were previously (only) in the webclient env.

Moreover, the PublicRoot no longer uses the ServiceProviderMixin,
such that services are only deployed once, in the (public) env.

Owl components can now be defined in the website, and rely on a
properly built env. Legacy widgets still works as they access
services through the PublicRoot (via trigger_up) which redirects
those requests to the env.

1 files changed, 5 insertions, 18 deletions

diff --git a/addons/web/static/src/js/public/public_env.js b/addons/web/static/src/js/public/public_env.js
index 373c7b512b8..581cccd430b 100644
--- a/addons/web/static/src/js/public/public_env.js
+++ b/addons/web/static/src/js/public/public_env.js
@@ -1,24 +1,11 @@
 odoo.define("web.public_env", function (require) {
     "use strict";
 
-    const { _t } = require("web.core");
-    const rpc = require("web.rpc");
+    /**
+     * This file defines the env to use in the public side.
+     */
 
-    const qweb = new owl.QWeb({ translateFn: _t });
+    const commonEnv = require("web.commonEnv");
 
-    function performRPC(params, options) {
-        const query = rpc.buildQuery(params);
-        return session.rpc(query.route, query.params, options);
-    }
-
-    // There should be as much dependencies as possible in the env object.
-    // This will allow an easier testing of components.
-    // See https://github.com/odoo/owl/blob/master/doc/reference/environment.md#content-of-an-environment
-    // for more information on environments.
-    return {
-        qweb,
-        services: {
-            rpc: performRPC,
-        },
-    };
+    return commonEnv;
 });