As I said, you need to put it in the doc comment of the _class_ even if
"@fn" is used in a method of that class.
I understand that it might be a bit tedious to update your code at first,
but being a bit stricter in the parsing process allows us to catch errors
early on. This will reduce the time that you spend with searching for
missing imports, typos, or just sitting there wondering why something
doesn't work.
Johannes
On Mon, May 23, 2011 at 5:26 PM, Roger Webb <webb.ro...@gmail.com> wrote:
> The comment in question is below. This is still throwing the same
> error. Also, it's generating this error based on the method. Will I
> have to put this annotation in every comment block that uses the "fn"
> annotation, or just in the first comment of the file?
>
> For the developers, it would IMHO be best if the Symfony/Doctrine
> annotations were namespaced and did not adversely affect annotations
> from other projects.
>
> /**
> * @IgnoreAnnotation("fn")
> * @fn loginAction
> *
> */
>
> Thank you for your help,
>
> Roger
>
> On May 23, 10:17 am, Johannes Schmitt <schmitt...@gmail.com> wrote:
> > Put an @IgnoreAnnotation("fn") in the doc comment of the class where this
> > annotation is used.
> >
> > Johannes
> >
> >
> >
> >
> >
> >
> >
> > On Mon, May 23, 2011 at 5:05 PM, Roger Webb <webb.ro...@gmail.com>
> wrote:
> > > Hey Everyone,
> >
> > > I'm using Doxygen for my documentation generation. I updated to Beta2
> > > and fixed all of the Doctrine annotations as described in the Update
> > > Document and found that all of my doxygen annotations are causing an
> > > exception to be thrown:
> >
> > > [Semantical Error] The annotation "@fn" in method ARN\UserBundle
> > > \Controller\UserController::loginAction() was never imported.
> >
> > > Any ideas on a workaround?
> >
> > > Roger
> >
> > > --
> > > 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 users" group.
> > > To post to this group, send email to symfony-users@googlegroups.com
> > > To unsubscribe from this group, send email to
> > > symfony-users+unsubscr...@googlegroups.com
> > > For more options, visit this group at
> > >http://groups.google.com/group/symfony-users?hl=en
>
> --
> 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 users" group.
> To post to this group, send email to symfony-users@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-users+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en
>
--
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 users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
