You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Nicolas Peltier (Jira)" <ji...@apache.org> on 2021/09/15 17:47:00 UTC

[jira] [Resolved] (SLING-10419) Script errors should give more context

     [ https://issues.apache.org/jira/browse/SLING-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Peltier resolved SLING-10419.
-------------------------------------
      Assignee: Nicolas Peltier
    Resolution: Fixed

> Script errors should give more context
> --------------------------------------
>
>                 Key: SLING-10419
>                 URL: https://issues.apache.org/jira/browse/SLING-10419
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Pipes 4.1.2
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>            Priority: Major
>             Fix For: Pipes 4.2.0
>
>
> Right now, in case an exception in a script is due to the context (current resource), there is no way to spot it but to switch to debug log. Last resource for which exception has occured would help here  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)