Hi all,
In the new React based dashboard widget is defined as a another React
component. ATM these widgets are basic React components which extends from
React.Component class.
But within these widgets we need to provide some extra capabilities for
widget developers such as providing mechanism to
+1, I think this will also help us to manage user-prefs in the future.
On Thu, Aug 31, 2017 at 1:44 PM, Lasantha Samarakoon
wrote:
> Hi all,
>
> In the new React based dashboard widget is defined as a another React
> component. ATM these widgets are basic React components which extends from
> Re
Hi All,
AFAIK shadow DOM not supported by many browsers ATM. Can't we simply use
unique ID and extend the class with ID to prevent the CSS conflicts.
Regards,
*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Associate Technical Lead
WSO2, Inc.
lean.enterprise.middleware
0771100911
Hi all,
We looked into the Shadow DOM approach, but as Dakshika mentioned it is
only supported by limited number of browsers resulting we cannot consider
it as a feasible solution.
There are couple of other popular approaches that we can follow in order to
achieve CSS isolation. *None of these ap
Hi Lasantha,
Could you please elaborate more on the css modules approach regarding the
use of webpack config for name spacing the css classes.
So that we can provide a sample webpack config for the widget authors to
refer when they are writing their widgets.
Thanks,
Tanya
On Wed, Sep 13, 2017 a
Hi Tanya,
Sorry for missing the required modifications in webpack.config.js in the
above mail.
Apart from the above mentioned code changes from in the React component and
the CSS stylesheet, widget author needs to do few modifications in the
webpack.config.js file as well. Those changes are as fo
