Hi! I've recently started dabbling in the module SDK as Element Web's customisations have been deprecated. On a custom fork, we used this customisations to essentially replace entire files within Element Web, replacing entire components with our owh versions to provide customized "anything" (styling, logic, etc).
customisations have been deprecated in favor of this module; there seems to be limited documentation on the module API as a whole, but from my experimenting / research I don't seem to find a way to accomplish the same behaviour we could with customisations.
If the case is that in fact it does not exist, I would propose an addition to such functionality - a way to replace entire components, be by extending them or replacing them in their entirety. This way the range of what the module API could achieve would be much more broad.
Hi! I've recently started dabbling in the module SDK as Element Web's
customisationshave been deprecated. On a custom fork, we used thiscustomisationsto essentially replace entire files within Element Web, replacing entire components with our owh versions to provide customized "anything" (styling, logic, etc).customisationshave been deprecated in favor of this module; there seems to be limited documentation on the module API as a whole, but from my experimenting / research I don't seem to find a way to accomplish the same behaviour we could withcustomisations.If the case is that in fact it does not exist, I would propose an addition to such functionality - a way to replace entire components, be by extending them or replacing them in their entirety. This way the range of what the module API could achieve would be much more broad.