[READY] Feature virtual dom transform

[FelipeSimoes]

1 - Virtual dom transformations by reducer
2 - Removal of component loader
3 - Updates on Component Base
4 - Updates on the grid in favor of CSS variables and one-level grid

Test URLs:

• Before: https://main--henkel-raqn-guide--hlxsites.hlx.page/
• After: https://feature-virtual-dom-transform--raqn-docs-sharepoint--henkel.aem.page/

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• 9ad279e ✅ (latest)
• d63e68f ✅
• c102766 ✅
• d7db927 ✅
• 17b8d9c ✅
• e285ff9 ✅
• b7d5a9d ✅
• be7be6c ✅
• c54de58 ✅
• 9c1826b ✅
• c1133b7 ✅
• ac8453d ✅
• 2c20c20 ✅
• 6ea38cf ✅
• 59fe2fa ✅
• acaf728 ✅
• d6930ab ✅
• a628b14 ✅
• 25e8fe3 ✅
• fd15ee9 ✅
• f464335 ✅
• 15742bf ✅
• 496bf88 ✅
• 351e42e ✅
• 8dd3d4e ✅

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/
🖥️	/

[infloent]

We have removed the usage of basepath in this PR #29

Should this be brought back?

[FelipeSimoes]

Yes, since on the other SharePoint configs are different, making things break when we have fixed paths like before

[infloent]

This should be moved in the setDefaults() method for consistency

[FelipeSimoes]

Actually, all those should be class properties.
To make sure they are defined before the constructor, for instance, if we need to override a property from HTMLElement that need to be set as normal OOP class prop before super is called

[infloent]

In my tests in the begining that worked as it was before, we could change from an element directly any of these properties.

And for config and nestedComponentsConfig which we are extending in components keeping the defaults from base, the extension failed if these were class fields.