-
-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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
Explanation for design patterns #590
Comments
Changed https://github.com/iluwatar/java-design-patterns/wiki/02.-Pattern-template a bit. There is no diagram anymore. Explanation section was added. |
This reverts commit fba30e5.
@iluwatar Hi, can I be assigned the reader-writer-lock pattern? |
@iluwatar Hi, can I be assigned to the data-mapper design pattern? |
Github doesn't allow me to add any more assignees, but consider yourselves hired @steph88ss and @XianWu99 |
I want to help in this issue |
@shubhig226 please mention the pattern you'd like to work on |
@iluwatar Can I please work on Producer-Consumer? |
Sure, go ahead @ManviGoel26 |
I have split up this issue into multiple independent ones e.g. "Explanation for Bridge". If you are working on some explanation, please comment on the new issue and I'll assign it to you. I'll close this task now. |
…tar#2170) * Update README.md * Update README.md * Add Explanation * Update README.md * Update README.md * Update README.md * Update README.md
iluwatar#2170)" This reverts commit 5e385d9.
…atar#2127)" This reverts commit c62bdf0.
We want to present the design patterns better as the current does not reach its goal of explaining how the pattern works in a simplest possible way. I'm hugely inspired by https://github.com/kamranahmedse/design-patterns-for-humans repository.
Let's do this by adding 'Explanation' section to the patterns'
README.md
file. For an example see http://java-design-patterns.com/patterns/bridge/.Let's track the issue progress here with the following checklist that indicates the patterns where explanation section is already available.
The text was updated successfully, but these errors were encountered: