[jira] [Created] (SLING-4442) Invalid parametrization of Sightly statements should lead to exceptions instead of errors

["Konrad Windszus (JIRA)" <ji...@apache.org>]

Konrad Windszus created SLING-4442:
--------------------------------------

             Summary: Invalid parametrization of Sightly statements should lead to exceptions instead of errors
                 Key: SLING-4442
                 URL: https://issues.apache.org/jira/browse/SLING-4442
             Project: Sling
          Issue Type: Improvement
    Affects Versions: Scripting Sightly Engine 1.0.0
            Reporter: Konrad Windszus


Currently invalid parametrization of Sightly statements only leads to errors/warnings in the log. Rather programmatic errors should lead to exceptions so that errors are detected earlier during development and to prevent invalid HTML output due to failures within a Sightly script (a HTML page with a 500 status is the right thing to do IMHO).

This affects e.g.
# data-sly-include with invalid/empty path
# data-sly-resource with empty path
# data-sly-call with invalid name (this does not even provide logging currently)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)