Closed
Description
I started this issue from the discussion here: php-http/HttplugBundle#81
Our BC promise in this library is the following functions:
HttpAsyncClientDiscovery::find();
HttpClientDiscovery::find();
MessageFactoryDiscovery::find();
StreamFactoryDiscovery::find();
UriFactoryDiscovery::find();
ClassDiscovery::setStrategies();
ClassDiscovery::clearCache();
// And the
DiscoveryStrategy interface
// And our exceptions and when they are thrown
This API has nothing to do with the discovery methods (strategies) itself. The strategy classes should not be a part of our API promise. Which is a great thing.
If we change the namespace of our clients we just add another "NewNamespacesStrategy" together with our existing CommonClassesStrategy
. Same with if Puli changes their API when they release 1.0. We just add a "Puli1Strategy".
So if we leave the strategies outside our BC promise, are we ready for a stable release? At least, can we mature in to this API and tag 1.0 after the summer?
Metadata
Metadata
Assignees
Labels
No labels