184 get issues by labels then save them to localdb #192
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.
COOL NEW FEATURE!!!!
Service name:
IGitHubIssueLocalDbService
Page name:
ActivityIndicatorPage
Contributors
Describe your changes
In the latest update, the mechanism for retrieving GitHub issue lists has been significantly optimized. Upon the initial visit to the respective page, issue data is now cached in a local database. Subsequent accesses to this page will leverage this cache to fetch issue information, bypassing the need for direct GitHub API calls. This approach enhances the application's performance and mitigates potential rate limiting issues associated with frequent API requests.
Feature
To facilitate these improvements, the feature logic has been modularized into a dedicated project,
MAUIsland.Features.LocalDbFeatures.GitHub
. This project works in tandem with the foundationalMAUIsland.Features.LocalDbFeatures
, ensuring a cohesive and maintainable codebase.Viewmodel
The implementation of this caching strategy is managed within the ViewModel. This design choice allows for a seamless integration with existing data retrieval processes, utilizing the IGitHubService for initial data acquisition from the GitHub API. This strategic placement of logic within the ViewModel layer ensures that our application remains responsive, efficient, and capable of scaling to meet future requirements.
Support functionalities
Usage (ViewModel):
Retrieve the github issues from cached first
Save issue down to the local database
Have we discussed about this before ? (Please link the discussion link below)
Yes in discord