-
-
Notifications
You must be signed in to change notification settings - Fork 557
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
Added json data in backend/caching.json #1591
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Thank you, Sahilll15, for creating this pull request and contributing to LinksHub! 💗
The maintainers will review this Pull Request and provide feedback as soon as possible! 😇
We appreciate your patience and contribution, Keep up the great work! 😀
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.
Here are some tweaks that I made to your description @Sahilll15. In the future, consider running your descriptions through Grammarly before adding them as PRs. Other than that, you're off to a great start! :)
Co-authored-by: Christine Belzie <105683440+CBID2@users.noreply.github.com>
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
Cool |
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.
@Sahilll15 thanks. Please read and follow the CONTRIBUTING guidelines to learn about category and subcategories.
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.
Hi @Sahilll15! :) I pointed out some proofreading errors that could be improved. Consider using Grammarly to help you revise them.
@CBID2 please have a look |
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
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
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.
have a look
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
I can't merge it @rupali-codes |
please merge it!! |
@k-deepak04 please review it! |
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.
🚀 Looks good to me.
Enhancing Backend Caching Information
Fixes Issue
Closes #1505
Proposed Changes
In this pull request, I have made substantial updates to the
database/backend/caching.json
file to improve the caching functionality in the backend.Changes Made
I have enriched the
caching.json
file with additional and comprehensive information about the caching mechanisms in the backend. This includes details about caching strategies, implementation approaches, and best practices for optimal performance. By providing this in-depth information, we aim to empower developers and team members to make informed decisions regarding caching in our backend system.Screenshots
Screenshot of the updated changes showcasing the added information.
Note to Reviewers
Dear Reviewers,
In this pull request, I have focused on enhancing the documentation related to backend caching in the
caching.json
file. The changes aim to provide a comprehensive resource for developers and team members to understand the caching implementation in the backend better.I have meticulously reviewed the content to ensure accuracy and clarity. The added information should serve as a valuable reference, especially for those working on optimizing backend performance.
Thank you for your time and consideration. Your feedback is highly appreciated.
Best regards,
[@Sahilll15]