Feature #36077

Separate original classes and proxy classes in class cache

Added by Lienhart Woitok over 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Should have
Category:
Object
Target version:
-
Start date:
2012-04-14
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

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.

#1

Updated by Gerrit Code Review over 9 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10500

#2

Updated by Gerrit Code Review over 9 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10500

#3

Updated by Gerrit Code Review almost 9 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10500

#4

Updated by Gerrit Code Review almost 9 years ago

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10500

#5

Updated by Karsten Dambekalns almost 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?

#6

Updated by Lienhart Woitok almost 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).

#7

Updated by Karsten Dambekalns over 8 years ago

  • Target version changed from 2.0 beta 1 to 2.1
#8

Updated by Robert Lemke about 8 years ago

  • Target version deleted (2.1)
#9

Updated by Christian Müller about 8 years ago

  • Status changed from Needs Feedback to Closed

I think the debugging proxy is the way to go, so closing this one.

Also available in: Atom PDF