Separate original classes and proxy classes in class cache
IDEs like PhpStorm get confused with code completion if proxy classes are known to the IDE. On the other hand, one can only set breakpoints in the original classes if those are known to the IDE. As long as proxy and original classes share the same cache directory one can not use both IDE features at the same time.
Updated by Karsten Dambekalns about 9 years ago
- Category set to Object
- Status changed from Under Review to Needs Feedback
- Assignee set to Lienhart Woitok
- Target version set to 2.0 beta 1
The questions is, do we want this? It feels "clean" to have proxy and "original" classes separated, but on the other hand having two caches adds some overhead and complexity. If the debugger proxy Sebastian used in http://blog.sandstorm-media.de/2012/08/debugging-flow3/ works fine, we'd not need this change for debugging.
So, what do you think?
Updated by Lienhart Woitok about 9 years ago
This change is older than Sebastians proxy. At that time, I just tried to get a solution to the problem, but if Sebastians proxy works reliably on all relevant platforms and environments (I haven't tested it yet), then I think this is not needed anymore as Sebastians approach is much more convenient (having breakpoints in the files you actually edit).