Bug #7198

Reflection Service should ignore leading backslashes in class names

Added by Robert Lemke over 5 years ago. Updated almost 5 years ago.

Status:Resolved Start date:2010-04-09
Priority:Should have Due date:
Assigned To:Robert Lemke % Done:

100%
Category:Reflection
Target version:TYPO3 Flow Base Distribution - 1.0 alpha 8 Estimated time:1.00 hour
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

While reflecting classes it could happen that the reflection service caches for example class names of interface implementations with or without a leading backslash, depending on how the class was specified in some annotation. This is error prone and therefore the reflectClass method should silently trim a leading backslash.

While at it, the Object Manager could give some hint in its API methods that an object could probably only not be found because a leading backslash was given - which is not allowed.

Associated revisions

Revision 7d6cb980
Added by Robert Lemke over 5 years ago

[+TASK] FLOW3 (Object): The Abstract Object Container now gives a hint / throws an InvalidArgumentException if object names or class names were specified with a leading backslash. Relates to #7198
[+BUGFIX] FLOW3 (Reflection): The Reflection Service now ignores leading backslashes in class names specified in annotations. Resolves #7198
[+BUGFIX] FLOW3 (Persistence): The Persistence Manager now retrieves repository objects by object name instead of class name. Resolves #7199

History

#1 Updated by Robert Lemke over 5 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r4043.

Also available in: Atom PDF