Hi Johannes,
Thanks for starting this discussion. This really is a problem right now.
2011/4/19 Johannes <johannes.schmitt...@googlemail.com>:
> 3) Importing annotations that are used in the class
>
> /**
> * @use("Symfony\Component\Validator\Constraints\*")
> * @use("Doctrine\ODM\MongoDB\Mapping\*")
> * @use("Doctrine\ORM\Mapping\*", alias="orm")
> */
> class A {
> /**
> * @Id
> * @orm:Id
> * @NotBlank
> */
> private $name;
> }
>
> Pros:
> - works always (no unsolvable conflicts)
> - very flexible
> - hard validation is possible
> - probably best forward compatibility if annotations are ever
> implemented on language level
>
> Cons:
> - harder to implement than 1)
I'm in favor of this solution. It's very clear and doesn't produce any
conflicts outside of the given file. The current way of having
predefine global prefixes just sucks when many people start using
(custom) annotations.
Bernhard
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
