Skip to content
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

Add Comprehensive Docstrings to Codebase #28

Open
AmrElsayyad opened this issue Jul 14, 2024 · 5 comments
Open

Add Comprehensive Docstrings to Codebase #28

AmrElsayyad opened this issue Jul 14, 2024 · 5 comments
Assignees
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@AmrElsayyad
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Currently, the codebase lacks comprehensive docstrings, making it difficult for developers to understand the purpose and functionality of various methods and classes. This can lead to confusion and increased time spent on code review and debugging.

Describe the solution you'd like
I propose adding detailed docstrings to all methods and classes in the codebase. These docstrings should follow a consistent format and provide clear explanations of the parameters, return values, and any exceptions raised.

Describe alternatives you've considered
Creating a separate documentation file is an alternative solution, but it might not be as effective as embedding docstrings directly within the code. Docstrings are more accessible to developers, making it easier for them to understand and maintain the code.

Additional context
Adding comprehensive docstrings will improve code readability and maintainability, making it easier for both current and future developers to work with the codebase.

@AmrElsayyad AmrElsayyad added documentation Improvements or additions to documentation good first issue Good for newcomers labels Jul 14, 2024
@abhi9720
Copy link
Owner

Hi @AmrElsayyad

That would be very best for new people and also helps us In debugging

We can start using the javadoc plugin in pom.xml file

What do you think about this ?

@AmrElsayyad
Copy link
Collaborator Author

Hi @AmrElsayyad

That would be very best for new people and also helps us In debugging

We can start using the javadoc plugin in pom.xml file

What do you think about this ?

Good idea. We can also add javadocs along with other changes when possible.

@ajaykathwate
Copy link

Hey @AmrElsayyad, Can I work on this ?
Can you explain this a bit more.

@AmrElsayyad
Copy link
Collaborator Author

AmrElsayyad commented Aug 6, 2024

Hey @AmrElsayyad, Can I work on this? Can you explain this a bit more?

Sure, go ahead!

@AmrElsayyad
Copy link
Collaborator Author

AmrElsayyad commented Aug 6, 2024

@ajaykathwate You need to add Javadoc comments to classes, methods, and attributes like this:

image

This will help you understand the project as you do. It's okay if you add some of them. You don't have to add them all. But please group your changes into meaningful commits so that it's easier to review.

Please let me know if you need any help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants