The migration checklist is designed to facilitate the transition of API-related tasks in our app from the current GitHub SDK file structure to a more organized and manageable class-based approach. This transition is crucial for implementing advanced features such as Enterprise service support (#111).
Objective for GitHub App Developers
As GitHub App developers, our goal is to systematically migrate all existing features to utilize a new, improved class structure. This will enhance code readability, maintainability, and scalability.
Tasks
[ ] 1. Get Settings: Retrieve BaseHost and BaseAPIhost from the Settings and store them persistently.
[ ] 2. Migrate GET Request
[ ] 3. Migrate POST Request
[ ] 4. Migrate Delete Request
[ ] 5. Migrate Patch Request
[ ] 6. Migrate Get user info method
[ ] 7. Migrate createSubscription method
[ ] 8. Migrate deleteSubscription method
[ ] 9. Migrate updateSubscription method
[ ] 10. Migrate addSubscribedEvents method
[ ] 11. Migrate removeSubscribedEvents method
[ ] 12. Migrate createNewIssue method
[ ] 13. Migrate getIssueTemplates method
[ ] 14. Migrate getIssueTemplateCode method
[ ] 15. Migrate githubSearchIssuesPulls method
[ ] 16. Migrate getRepoData method
[ ] 17. Migrate mergePullRequest method
[ ] 18. Migrate approvePullRequest method
[ ] 19. Migrate getBasicUserInfo method
[ ] 20. Migrate getUserAssignedIssues method
[ ] 21. Migrate getIssueData method
[ ] 22. Migrate addNewPullRequestComment method
[ ] 23. Migrate getPullRequestComments method
[ ] 24. Migrate getIssuesComments method
[ ] 25. Migrate addNewIssueComment method
[ ] 26. Migrate getPullRequestData method
[ ] 27. Migrate getRepositoryIssues method
[ ] 28. Migrate updateGithubIssues method
[ ] 29. Migrate isRepositoryExist method
By systematically completing these tasks, we ensure a smooth transition to the new class-based structure, paving the way for enhanced functionality and future development.
Migration Checklist
Purpose
The migration checklist is designed to facilitate the transition of API-related tasks in our app from the current GitHub SDK file structure to a more organized and manageable class-based approach. This transition is crucial for implementing advanced features such as Enterprise service support (#111).
Objective for GitHub App Developers
As GitHub App developers, our goal is to systematically migrate all existing features to utilize a new, improved class structure. This will enhance code readability, maintainability, and scalability.
Tasks
BaseHostandBaseAPIhostfrom the Settings and store them persistently.By systematically completing these tasks, we ensure a smooth transition to the new class-based structure, paving the way for enhanced functionality and future development.