0
 Followers
4
 Likes

Faster way to test UI changes

1CP
New

Publishing a module takes too long (especially if you have to do merge with other people's code) just to test simple UI changes. 

A probable solution would be to do branching (at least to avoid the merging part).

Maybe a better solution might be for the system to detect what changes were made and only publish those changes. For example if only CSS changes were made, we could just update the CSS instead of doing the full publish. 

Created on 3 Oct 2018
Comments (1)

Changed the category to 1CP


views
139
Followers
0