October 18, 2018 in Developer Connection
I've run into this far too often, trying to have a theme and app developed at the same time, and the two clash with each other.
The problem is this, the structure for IN_DEV and Designer mode are different from each other, which forces at least 3 sub-repo (css/html/resources) along with the theme's repo and the app's repo. then this becomes increasing ludicrous, when there is more than one app is being developed. you'd end up having at least 9 repo's ( 6 for the css/html/resources, 2 app repo's, 1 theme). We could also just have 1 repo, where we just push everything to it (including IPS files), but this has its own set of problems. It is time consuming as it is to handle conflicts from push's when the changes are coming from the same file, its an added layer of work that is very time consuming to do a diffs on two files from separate directories and then verify that both files are in sync after wards, this really hampers the workflow from day to day.
The system, imho, when you are working on one at a time is fine. it makes sense, or if you bring one in after the other, but trying to develop them concurrently is very inefficient and in most cases, goes from "complicated" to "ludicrous to gone plaid" (if you get that joke, my hats off to you fellow traveler).
The suggestion i have, i believe would be the easiest to implement, change the file structure for Designer mode to disk, instead of:
this way it is setup more like the dev folder, reducing the number of sub repo's per app from 3 to 1. also include the JS for the third party apps, so front end dev's can more easily add/edit/remove them if need be.
This topic is now archived and is closed to further replies.
Started 12 minutes ago
Started Thursday at 01:08 PM
Started November 17