[Bug] Default *DataProvider priority is the same than custom Providers

[Cethy]

Since I updated to v2.3.5, the order of my project's DataProvider is messed up : the default CollectionDataProvider is tagged before my custom ones, so it is called instead.

As per the documentation, one will expect the custom DataProviders to be always called before the default ones. Additionally, this is really error-prone since it could be hard to catch.

Shouldn't the default DataProviders have a negative priority by default ?

[mmarynich]

@Cethy Read it, solution is here symfony/symfony#29836

[Cethy]

@mmarynich Thx a lot for the read. :)

I'll keep explicit configuration for now then (positive priority for custom DataProvider).
But I still think API-Platform should be patch to not rely on the magic default sorting mechanism (opposed to explicit priority).

[mmarynich]

@Cethy I completely agree with you.
@dunglas What do you think about this ?

[mmarynich]

I have done a PR
symfony/symfony#29853

[suyar]

I think it should be fixed.