Improve debugging "experience" in IDE (java assist)
---------------------------------------------------
Key: TAPESTRY-1859
URL: https://issues.apache.org/jira/browse/TAPESTRY-1859
Project: Tapestry
Issue Type: Improvement
Affects Versions: 5.0.6
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
