Closed Bug 874539 Opened 12 years ago Closed 9 years ago

Invalid LESS configurations during DEBUG should emit a warning

Categories

(support.mozilla.org :: Code Quality, task)

Product:
support.mozilla.org
Component:
Code Quality
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: shuhao, Unassigned)

Details

(Whiteboard: u=dev c=general p= s=)

Invalid LESS configurations without warning makes it difficult for new contributors to figure out why the site stays unstyled. A warning should be emitted that tells the contributor what is wrong (LESS_BIN is invalid, missing, LESS_PREPROCESS is False, and so forth)
PR: https://github.com/jsocol/jingo-minify/pull/50
Status: NEW → ASSIGNED
Hi :Pwnna. I am not LESS master and do not know, how can this affect the contributors or what should the fix look like. After three years from the initial PR, are there any updates? Maybe I would rather close this bug, as it would need to be fixed outside of Kitsune anyway.
Flags: needinfo?(shuhao)
I don't really remember this anymore. I probably had some weird configuration on my machine back then that caused some issues. It's probably safe to just close this.
Flags: needinfo?(shuhao)
Assignee: shuhao → nobody
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.