Create an architecture for the data flow for the widget properties and configuration.
Remove properties from the DSL which do not need to be stored on the servers. -- This will reduce the size of the DSLs and make sure that we're differentiating between properties pertinent to the layout and widget functionality, and the widget related configs used in the UI; or only needed during runtime and can be loaded during widget registration
The properties which we can avoid storing in the DSL are:
Is there an existing issue for this?
SubTasks