-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Document agreed Java guidelines to README.md #221
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
Labels
Comments
I can live with the Google guide. |
Maybe we can change this issue title to document the agreed conventions to |
Closed
@iluwatar I have changed the title. Should we target formatting existing pattern implementations with this issue? |
npathai
added a commit
that referenced
this issue
Aug 20, 2015
Agreed guideline is conveyed and configuration link for eclipse and IntelliJ is also added.
I think we should. But this can be another task. |
@iluwatar Sure. Maybe I will be able to squeeze in some time this weekend for it. |
pratigya0
pushed a commit
to pratigya0/java-design-patterns
that referenced
this issue
Aug 3, 2023
…uwatar#221) * Edited couple answers in the Network section * Edited Latency, Throughput and bandwidth * Edited few more answers in the Linux section * typos
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To keep the things in sync and properly formatted we need to follow some style guide.
My vote is for Google Style Guide as it is used in many open source projects. Other option is to follow Oracle coding convention.
Google Style guide configuration for IDE
Tasks to complete
The text was updated successfully, but these errors were encountered: