http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DCOM-6 Doctrine Common <p>@nonalias:Annot results in a php notice.</p> DCOM-6

Non existant namespace alias throws a PHP Notice

Bug Major Resolved Fixed Benjamin Eberlei Tim Nagel Thu, 27 May 2010 04:37:37 +0000 Wed, 1 Sep 2010 13:13:34 +0000 Wed, 1 Sep 2010 13:13:34 +0000 2.0.0-BETA2 2.0.0-RC1 0 0 <p>Proposed tests and fix</p> <p><a href="http://github.com/merk/common/commit/65e8c10b74201c39dbe291c36230205d9b08ed65" class="external-link">http://github.com/merk/common/commit/65e8c10b74201c39dbe291c36230205d9b08ed65</a></p> <p>In commit: <a href="http://github.com/doctrine/common/commit/ad49a676269af368563bd9a848c904b81a825622" class="external-link">http://github.com/doctrine/common/commit/ad49a676269af368563bd9a848c904b81a825622</a></p> <p>I fixed this issue.<br/> The validation on unexistent classes cannot be done correctly, otherwise it'd conflict with phpDoc tags.</p> <p>What will your change do if there are multiple implementations of the Reader working on entities that dont have common namespaces, but still use namespaces?</p> <p>Would it not make more sense to skip something that the Reader doesnt understand, rather than throwing an error?</p> <p>(For example, Symfony2's validator system might have namespaced validators, which would then cause the 'Doctrine' reader to throw an exception)</p> <p>Yes, you're right...</p> <p>I think we'll have to silently bypass unknown aliases... this makes debug harder, but we don't have any other option. =(</p> <p>Reopening it</p> <p>Fixed to skip the unknown alias annotation.</p>