Konrad Podgórski 74d30d9e39 Option to set requirements and parameters directly from ApiDoc annotation ... Sometimes required parameters are not used through routing but still they are mandatory. I wanted to have API with resource.json?foo=bar&something=else format, that was possible through QueryParam annotation or requirements in routing BUT! There was no way to set dataType or description This PR solves problem for me. Side note: if you want to declare e.g. _format requirement through Annotation or any other param that is used in url ({foo} format) then it won't work. Because Bundle still overrides requirements and parameters after the constuctor in ApiDoc is called. This might be solved in separate PR by adding check if given requirements or parameters was already defined.		2013-10-15 15:28:54 +02:00
..
Components	Added support for the jms version annotations in formatters	2013-05-12 14:54:01 +02:00
layout.html.twig	make api method headers anchor links so a speicif method can be refered to through its unique id	2013-09-06 13:42:19 +02:00
method.html.twig	Option to set requirements and parameters directly from ApiDoc annotation	2013-10-15 15:28:54 +02:00
resource.html.twig	Used Twig instead of plain PHP in the HtmlFormatter. Fixes #1	2012-04-13 11:25:53 +02:00
resources.html.twig	Fixed condition to display resource url (fixes #146)	2013-03-20 10:02:20 -03:00