Hello again,
In keeping up with the updates from Zero releases, we ran into a road-block on being able to customize and tweak the Metronic themes due to merge-conflicts that could arise from theme changes that were made for the newest version. This will probably continue to be an ongoing conflict, as newer implementation strategies might change some components and theme items, so we were wondering what we could do on our side to make these merges easier going forward regarding customizing the theme.
- There was an idea about duplicating components we wanted changed and referencing the HTML files or items for those components from the TS files supplied (but this falls back into conflict if logic changes are ever introduced)
- Compiling the final theme and all overrides and appending the CSS last when loading the application (but could fall to specificity and CSS engine parsing)
Any ideas or solutions that would allow someone to create and use a Custom Metronic theme/style (even if through the MetronicThemeChanger) to cut down on customization conflicts when merging major releases.
Thanks
1 Answer(s)
-
0
Hi @dev_frontrush
First of all, we also don't want to upgrade if Metronic makes such major changes in the future. This is not %100 certain at the moment but we think that way.
To be honest, we couldn't find aa good way to overcome this problem until now except manually merging the changes.
