Due to the last conversation on the Zoom meeting, I decided to separate the function names rename from the error handling PR I opened in #76. This makes it easier for the continuous topic-based merging currently being done by @the-mayer.
What kind of change(s) are included?
[ ] Feature (adds or updates new capabilities)
[ ] Bug fix (fixes an issue).
[x] Enhancement (adds functionality).
[ ] Breaking change (these changes would cause existing functionality to not work as expected).
Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.
[x] I have read and followed the CONTRIBUTING.md guidelines.
[x] I have searched for existing content to ensure this is not a duplicate.
[x] I have performed a self-review of these additions (including spelling, grammar, and related).
[x] I have added comments to my code to help provide understanding.
[ ] I have added a test which covers the code changes found within this PR.
[x] I have deleted all non-relevant text in this pull request template.
Yes as @the-mayer said, this pr is solely for renaming functions. The other pr #76 is for error handling @jananiravi. This would make it easy for David to merge them on the basis of a specific issue.
Description
Due to the last conversation on the Zoom meeting, I decided to separate the function names rename from the error handling PR I opened in #76. This makes it easier for the continuous topic-based merging currently being done by @the-mayer.
What kind of change(s) are included?
Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.