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

..

Annotation

Option to set requirements and parameters directly from ApiDoc annotation

2013-10-15 15:28:54 +02:00

EventListener

Remove .{_format} from routes used for resource grouping

2012-08-10 11:38:01 +02:00

Extractor

Adding test for named resource

2013-10-11 16:18:02 +02:00

Fixtures

Option to set requirements and parameters directly from ApiDoc annotation

2013-10-15 15:28:54 +02:00

Formatter

Adding test for named resource

2013-10-11 16:18:02 +02:00

Parser

Can now specifiy form name

2013-10-08 12:09:46 -07:00

bootstrap.php

Fixed the bootstrap of the testsuite

2012-06-20 22:53:27 +02:00

TestCase.php

Added tests for the ApiDoc annotation

2012-04-13 15:20:45 +02:00

WebTestCase.php

Remove scope hack since 2.3 has been fixed

2013-05-10 10:34:21 +02:00