-
Notifications
You must be signed in to change notification settings - Fork 523
Add a ResultFactory to easily create ResultInterface instances #182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Why you don't add a ResultFactoryInterface? |
|
What would be the use case? I don't want people to define another On Wed, Jan 16, 2013 at 10:29 PM, Markus Bachmann
|
|
Yes, make sense. Maybe the best implemention currently. |
Add a ResultFactory to easily create ResultInterface instances
|
I like this a lot !! That's cool :) Now, we just need to implement Should the method |
|
@toin0u I think the provider should not decide which result should be generated. The developer should decide which @willdurand Do you agree? |
|
The provider won't decide which result should be generated, never. @Baachi could not have been more right, thank you! |
|
@Baachi I see your point and of course I don't think the provider should decide which |
|
With:
I meant that users should do this not Geocoder ! Sorry, my bad... |
|
ah yes ;) On Thu, Jan 17, 2013 at 3:47 PM, Antoine Corcy notifications@github.comwrote:
|
|
I should read my comment twice.. :S |
|
No problem :) |
ping @Baachi, @toin0u
see #181
WDYT?