-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Implement _check #2217
Implement _check #2217
Conversation
Thank you for the submission, @Xantass! I'll review your code shortly, hang tight. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Thanks for your contribution @Xantass!
Your code style completely follows the style guide. Nice job!
All the tests are passing. Nice job!
🎉 You did it! 🎉You're an open source contributor now! Whether this was your first pull request, or you’re just looking for new ways to contribute, I hope you’re inspired to take action. Don't forget to say thanks when a maintainer puts effort into helping you, even if a contribution doesn't get accepted. Open source is made by people like you: one issue, pull request, comment, and +1 at a time. What's next?Find your next project:
Learn from other great community members:
Elevate your Git game:
Questions? Comments? Concerns?I'm always open to feedback. If you had a good time with the exercise, or found some room for improvement, please email me. Want to start over? Just delete your fork. |
#1
This Pull Request addresses the issue of code repetition in the codebase by moving duplicate error checking code to a dedicated function, _check(). This refactoring will make our codebase cleaner and easier to maintain as we continue to develop our calculator application.
Here's a summary of the changes made:
Moved duplicate error checking code to the _check() function
Invoked the _check() function within each relevant function
This should improve the readability and maintainability of our code, in line with the contribution guidelines.
For more details, please refer to the associated issue for this Pull Request.
Thank you for your attention and feedback!