update count key in the response #171
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Date: 27/11/2023
Developer Name: @sumitd94
Issue Ticket Number
Description
the count key in the response was returning the total number of counts the user has used for purging the cache, but ideally it should be giving us the remaining count the user has left with in purging cache
Documentation Updated?
If your feature adds a new API, then documentation related to the feature like API-Contracts, and Data-models must be updated.
Breaking Changes
If your feature introduces breaking changes or if something is missing, please mention the related issue tickets.
Development Tested?
Confirm whether the changes have been tested locally during development.
Tested in Staging?
Indicate whether the changes have been tested in the staging environment.
Under Feature Flag
Specify if the changes are currently under a feature flag.
Database Changes
Indicate whether the changes include modifications to the database.
Screenshots
Attach any relevant screenshots, such as test coverage reports, before and after images, or other visual aids.
Test Coverage
Provide information on the test coverage for the changes made in this PR. Include details on the types of tests conducted and their outcomes.
Additional Notes
Include any additional notes, considerations, or explanations that might be helpful for reviewers.