Open GoogleCodeExporter opened 8 years ago
[deleted comment]
Could you provide some examples? (resource content, processors being used,
etc)...
Original comment by alex.obj...@gmail.com
on 27 Nov 2014 at 9:58
[deleted comment]
[deleted comment]
If a processor produces an error message because of a syntax error in the
source it's processing, then that message is it's relevant for the developer.
For example, this invalid CSS:
p {{}
Would log something like
"file.css:123:3 Expected a property or "}": p {{}
in the server log.
If that messages instead was delivered to the browser, it would be much easier
to spot and correct.
It would be useful for all kinds of processors when running using the filter
(not maven).
Original comment by jens.ask...@gmail.com
on 27 Nov 2014 at 10:08
A generic error handling mechanism would be an useful feature. But, in the end,
it is really each processor job to decide how to handle an error. It would be
easily to implement a small change on a specific processor, rather than
providing a generic mechanism to handle all kind of exceptions for all
processors....
Original comment by alex.obj...@gmail.com
on 27 Nov 2014 at 10:11
Original issue reported on code.google.com by
jens.ask...@gmail.com
on 27 Nov 2014 at 9:56