Update abstract_factory more elaborate#370
Merged
Merged
Conversation
9e723e7 to
f72b1ba
Compare
Contributor
Author
|
And one question, why don't you use parent class? I know delegation is better than inheritance in many cases, but in this case I think the parent class |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After reading #366, I think it is not necessary to add more types of things but it can be more clear.
2 Points.
I think abstract factory can offer a concrete factory which can provide some different things from input/choice.
Then how about change show_pet() into something which can accept args like
name?abstract factory should have
abstract_factory,concrete_factoryandproducts.And in former abstract_factory.py
products is not clear.
So I returned Pet Object to make more clear what product is.