Repo::forIssues() misses some issues when closing issues #1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
as the issues get closed, more appear on the page, which means they dissapear of the next page so they essentially get missed from the loop where forIssues loops
c468275075/src/Repo.php (L16)
forIssues() misses some issues when closing issuesto Repo::forIssues() misses some issues when closing issuesThis is by design.
https://github.com/go-gitea/gitea/issues/8022
Either account for this in the app using this library. Or maybe implement some sort of delayed write / cache.
Think this is still needed. The forIssues() function can miss a lot when changing labels, titles, deleting etc. See the delete_* examples.
Maybe we do load all into memory before processing.
Maybe we leave forIssues() as it is, and add a new getIssues() that will fetch and return them all!? Then the user has a choice.
Done on develop. Will be in v1.2.1