Shorten the logged names of HBar Rate Limiting repositories.

[ebadiere]

🆕🐥 First Timers Only

This issue is reserved for people who have never contributed to Hedera or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'Good First Issue' is to help you make your first contribution to Hedera.

👾 Description of the issue

The current logger configuration uses logger.child({ name: 'hbar-spending-plan-repository' }). This may not be necessary and can make it harder to associate logs with their code sources. Simplifying the logger name for spending plans will improve readability.

Proposed Solution:

Update the logger configuration across the codebase, replacing instances of logger.child({ name: 'hbar-spending-plan-repository' }) with logger.child({ name: 'hbar-spending-plan' }) as shown below:

- logger.child({ name: 'hbar-spending-plan-repository' })
+ logger.child({ name: 'hbar-spending-plan' })

Example Implementation

Refactor the logging configurations by replacing 'hbar-spending-plan-repository' with 'hbar-spending-plan' across all relevant files.

📋 Step by step guide to do a contribution

If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. More information and concrete samples for shell commands for each step can be found in our CONTRIBUTING.md file.
A more detailed general documentation of the GitHub PR workflow can be found here.

• Claim this issue: Comment below that you are interested in working on the issue
• Wait for assignment: A community member with the given rights will add you as an assignee of the issue
• Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
• Check out the forked repository
• Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
• Solve the issue in your branch.
• Commit your changes: Here, it is needed to add sign-off information to the commit to accept the "Developer Certificate of Origin" (https://developercertificate.org). More details can be found in our CONTRIBUTING.md
• Start a Pull Request (PR): We have a pattern for naming pull requests that a GitHub Action checks. We use that pattern to support the creation of automatic release notes.
• Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the Hedera developer community for support.
• Wait for reviews: Members of the Hedera developer community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
• You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of the Hedera community as an open-source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽

🤔 Additional Information

If you have any questions, just ask us directly in this issue by adding a comment. You can join our community chat at Discord. A general manual about open-source contributions can be found here.

[Ritesh-Udgata]

kindly assign me to this issue

[quiet-node]

@Ritesh-Udgata Thanks for the initiative! Assigned the ticket to you!

[belloibrahv]

@quiet-node I want to know if this ticket is still available to work on.

[quiet-node]

@belloibrahv Heyy thanks for the initiative but seems like @Ritesh-Udgata has already been assigned to the ticket.

[quiet-node]

@belloibrahv I'd suggest a more fun and slightly more challenging, yet still beginner-friendly, option is this ticket #3142. If you're interested in working on it, please comment on the ticket, and I can update it to be Hacktoberfest-oriented and assign you to it! I’m also available to assist you along, just like last time with the logging issue.

[quiet-node]

Hello @Ritesh-Udgata, I wanted to check in and see if you are currently working on this or planning to do so.

[Ritesh-Udgata]

Yes I can continue working on it.

…

On Wed, Nov 27, 2024, 3:40 AM Logan Nguyen ***@***.***> wrote: Hello @Ritesh-Udgata <https://github.com/Ritesh-Udgata>, I wanted to check in and see if you are currently working on this or planning to do so. — Reply to this email directly, view it on GitHub <#3134 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AURMWC467J5TO5BKP34KQAL2CTWU3AVCNFSM6AAAAABQKPHMU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBSGAZTIOJSHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>