Skip to content

Decoupling of layout definitions #698

@EliasZ

Description

@EliasZ

With the whole new spirit of loosely coupling the Magento 2 code base, maybe a good look can be taken at the layout definitions and its dependencies. For example, opening Magento/Backend/view/adminhtml/layout/default.xml reveals the following definitions which can be moved:

<link src="Magento_Rule::rules.js"/> <!--Magento_Rule can take care of this--> 

The following can be moved to Magento_RequireJS:

    <link src="requirejs/require.js"/>
    <link src="mage/requirejs/resolver.js"/>
</head>
[...]
<block name="require.js" class="Magento\Backend\Block\Page\RequireJs" template="Magento_Backend::page/js/require_js.phtml" />
[...]
<referenceContainer name="after.body.start">
    <block class="Magento\RequireJs\Block\Html\Head\Config" name="requirejs-config"/>

More in after.body.start:

<block class="Magento\Translation\Block\Js" name="translate" template="Magento_Translation::translate.phtml"/> <!--Magento_Translation can take care of this-->

And so forth.

Metadata

Metadata

Assignees

Labels

Issue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentimprovement

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions