Switching to mobile-l Use global less import paths. I wrote this in a fixme in my hot fix yesterday :) On 10 Oct 2014 12:22, "Yuvi Panda" <[email protected]> wrote:
> Another option is to merge MobileApp back into MobileFrontend, but that > might be a bad idea for code hygiene reasons (and would also mean Mobile > Web team would be responsible for maintaining that part). > > On Sat, Oct 11, 2014 at 12:51 AM, Yuvi Panda <[email protected]> > wrote: > >> Yay to componentization! >> >> I'm wondering how to best depend on the styles from MobileApp in a >> forward compatible way. Mooching off MF's module definitions comes to mind, >> as does maintaining an array of file paths in MobileFrontend and >> referencing them in MobileApp. Other suggestions? >> >> On Sat, Oct 11, 2014 at 12:20 AM, Rob Moen <[email protected]> wrote: >> >>> If you depend on some of the LESS files in MobileFrontEnd (Apps) You >>> may want to know about the recent changes. >>> >>> TLDR: Content specific less was split from common.less and >>> main.less into separate files. >>> >>> Below are the related changes: >>> >>> https://gerrit.wikimedia.org/r/#/c/165850/ >>> https://gerrit.wikimedia.org/r/#/c/165851/ >>> https://gerrit.wikimedia.org/r/#/c/165852/ >>> https://gerrit.wikimedia.org/r/#/c/165853/ >>> https://gerrit.wikimedia.org/r/#/c/165854/ >>> https://gerrit.wikimedia.org/r/#/c/165855/ >>> https://gerrit.wikimedia.org/r/#/c/165856/ >>> https://gerrit.wikimedia.org/r/#/c/165857/ >>> https://gerrit.wikimedia.org/r/#/c/165858/ >>> >>> >>> -- >>> Rob Moen >>> Wikimedia Foundation >>> [email protected] >>> >> >> >
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
