[jira] Updated: (TAP5-118) Improve debugging "experience" in IDE (java assist)

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship updated TAP5-118:
--------------------------------------

    Issue Type: New Feature  (was: Bug)

> Improve debugging "experience" in IDE (java assist)
> ---------------------------------------------------
>
>                 Key: TAP5-118
>                 URL: https://issues.apache.org/jira/browse/TAP5-118
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Ognen Ivanovski
>            Priority: Minor
>
> If possible, improve step-into debug info in proxies and bindings. Typical usage scenarios are: 
>  - trying to step into a binding (the debugger should jump directly into the getter method)
>  - trying to step into a call to an injected service or component
>  - trying to step into a call to a service through a tapestry-ioc proxy 
> In the last two cases the debugger would 
>  - directly go to the service method implementation
>  - if the service is not already created it would jump to the service creation method (or constructor if bind() is used)
>    - upon return from the creation method / constructor it would directly go to the service call
> The general idea is not to allow the developer to step into java assist code. 
> This would greatly improve the ease-of-development as well as the  learnability of tapestry (as newbies often resort to the debugger to see "what's going on inside").

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org