[Hydra] add collection flag in documentation properties

[fmata]

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets	#912
License	MIT
Doc PR	n/a

Today it's impossible to know if an Hydra property is a collection of * or not.
I implemented the solution provided on https://lists.w3.org/Archives/Public/public-hydra/2017Jun/0010.html.

• Add tests
• Update tests

[fmata]

@dunglas, can you look quickly before I update the test suite ?

[dunglas]

Is this part really necessary (null !== $className = $type->getClassName()) && $this->resourceClassResolver->isResourceClass($className)?
Even if it is not a resource, the max cardinality is 1 if it's not a collection isn't it?

[dunglas]

Looks good to me @fmata. Great job!

[dunglas]

@fmata do you think you can finish this one soon? I would like to include it in 2.1 beta 2 (it is important for our client-side tools).

[fmata]

@dunglas yep but I encounter some problem with the test suite on my setup, many errors or fails unrelated

Unable to parse file "/home/path/api-platform-core/src/Bridge/Symfony/Bundle/DependencyInjection/../Resources/config/filter.xml"

Method Double\Symfony\Component\DependencyInjection\ContainerBuilder\P561::registerForAutoconfiguration() is not defined

...

Method Double\Symfony\Component\DependencyInjection\ContainerBuilder\P566::registerForAutoconfiguration() is not defined

Undefined class constant 'PARSE_KEYS_AS_STRINGS'

I use phpunit in vendors or the bridge.

Tests on Travis fail because order in array keys are not respected :/
Your help is welcome :)

Edit: strange, tests are green now but I changed nothing...

[dunglas]

@fmata try to run composer update before running the test suite.

[dunglas]

Thank you very much @fmata!