Repository navigation
overlays: GitHub REST collection completeness - #604
Merged
Merged
Conversation
The counterpart of the github-issues completeness overlay (#534) for the full api.github.com document: issues absent removed, notFound unavailable, no gone; comments the same plus parentAbsent. Same GitHub reference; the paging sentence says it is the issue after a deleted one that can be skipped. Tested with crud-causality v2 and v1. Not selected by a catalog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mpleteness # Conflicts: # overlays/README.md
- Merged main: #617's Todoist row joins the table (four overlays with this one; five once #586 lands), and the test list names both. - The "Issues" quote is verbatim now (double quotes, as the docs). - "Issues are disabled for this repo" is in neither the docs nor the pinned OAD: the overlay cites Create an issue's "If issues are disabled in the repository, the API returns a 410 Gone status." and marks a read's 410 and its body as not verified; the test relies on no body text. The README notes that #534's published GitHub Issues overlay makes the same claim (declaration unaffected: a 410 is unavailable either way). - Cites Using pagination in the REST API for page-number paging. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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.
Completeness overlay for GitHub REST (
overlays/APIs/github.com/api.github.com/1.1.4/completeness-920631db…-overlay.yaml). It makes the same declaration as #534's github-issues overlay, from the same GitHub reference:absent: removed,notFound: unavailable, nogone;parentAbsent: unavailable.The paging note is stated as GitHub documents it: the issue after a deleted or transferred one can be skipped, and it still exists.
overlays/tests/test_github_rest_completeness.py:classify_readoutcomes for 301, 404, 410 and 200, and the comments' parent.README: a row in "Collection completeness". It will conflict by one line with #586's row; whichever lands second takes both.
🤖 Generated with Claude Code