Best practice installation advice for zero initial negative impact, adding a component at a time to a mature code base
SynthesisDev opened this issue · 0 comments
Hi folks!!
I am wondering if I could ask for a pointer or two on integrating Cirrus into an already very customized app.
My clients just wanted to pick a component or two at a time to integrate it and I have been searching for the best means to do so.
Unfortunately, importing globally on the app had a relatively complex impact due to various conflicts of styles. I am resolving them one at a time currently but I know there are better ways.
What I tried
I tried first and foremost reading through the documentation and tried to import via node js and to use the config file. The import failed due to, most likely, my transition to an M1 machine and whatever configuration overhaul that requires.
So currently I am importing via the html style import link, but I would really love it if the config file could work because I really dont need global style overrides, and half of my work currently is hunting down places where the cirrus code is applying and overriding it.
This brings the question up about downloading and adding the files manually to my app, thoughts? That would, theoretically, provided the code is not minified, provide the means to just go comment out css applied to body tags etc.
When I tried the config file it had apparently zero impact. I interpret that to mean that either
- I need to validate it, its not structured correctly ( can it be validated somewhere? )
- or the config file will not impact imports via the html import style ( is this true? )
What is the simplest approach if I want to have zero impact on current code, but just bring in, for example, some fonts, buttons, and panels?
I imagine with the node style import I could import it directly to the components I am using, but intuitively I imagine that might bloat the app, to be pulling from the entire css library in many places, eventually.
Any help is greatly appreciated!