brunoais wrote:When there's errors in the CSS, the browser only reports them in the "compiled" CSS. How do you expect the style author to relate the different lines?
If it is constantly minified, how can the line number be useful when debugging and when checking for inconsistencies?
If someone like me finds an error in his version, there's no "unminified" version available. Are you forcing me to download another "full version" just to test and reproduce the error? I'd rather just flip the value of a constant and try again to gather as much material as possible. Having to download a "sister" version, clone the DB, install it, etc... Is a HUGE pain. Don't forget that I'd have to repeat the steps to get the error so I need first to reproduce the error multiple times until I pinpoint the issue to report it. If I don't do it in a clone of the original one, I can easily end up killing my live version.
LESS has had support for source maps since November 2013.
Ah! So you mean that both minified and unminified version are chipped with phpBB?
I made some research given that,
I wasn't updated on the source map for CSS, only the sourceMap for JS (I guess it's for both, not just js after all).
So you mean that everybody (not just web dev) will have to setup such that, every time a change happens, it must activate (manually or automatically) gulp for the changes he does?
Does that mean that a new requirement for styles will arrive such that style authors become obliged to use gulp no matter what they prefer to use?
The process for this feels pretty straight forward. Why not let phpBB do it itself? I already know about gulp's existance and I think I have a good idea of what it does. Are you sure it is a good idea for a project that like phpBB? Looks good for a private project in a company or when the project is closed source but an open source where many many people change it, are you sure? It is already a PITA(!)
having to deal with composer and its issues but, at least, it is a 1 time thing. Gulp requires setup to run manually or automatically (I didn't find a fully automated way to run it automatically on file changes (nearest one: https://www.npmjs.org/package/gulp-watch
So I say it again, gulp seems nice for projects with a stable group of people or only web dev kind of people working on it. I don't think that the casual user who just wants to tweak a color of the background or make some minor adjustments to the style will ever want to meddle with that. By forcing to use gulp to get the desired results, we no longer can say that making changes to the styles is direct and easy. It may still be easy but it is not even near of direct. Given that I still wonder if it still makes sense to tell others to do the tweaks (to the styles) themselves if they want to.