> > Dependency shouldn't have to agree to anything, that's the whole meaning > of dependency. eg: if you are using apache HTTP client as a dependency, > apache HTTP client team doesn't have to agree to any contract, you have to. > Contract is offered by the dependency and followed by the dependent, not > the other way around.
Agreed. But in this scenario, I don't see any other viable solution (if you have one, please suggest :) ). In the final web app, every page should have the same look & feel (same theme), otherwise UX will be broken. To achieve a same look & feel in both pages coming from the app & pages coming from dependency component, app and dependency component need to agree to use the same theme (same set of CSS classes). On Mon, Jan 23, 2017 at 9:49 PM, Manuranga Perera <[email protected]> wrote: > > When you import another component in your app as a dependency, your app >> and that dependency agree to use the same theme as your app > > > Dependency shouldn't have to agree to anything, that's the whole meaning > of dependency. eg: if you are using apache HTTP client as a dependency, > apache HTTP client team doesn't have to agree to any contract, you have to. > Contract is offered by the dependency and followed by the dependent, not > the other way around. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > -- Sajith Janaprasad Ariyarathna Software Engineer; WSO2, Inc.; http://wso2.com/ <https://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
