Repository navigation
Remove OAD overlays now hosted in the overlays repo - #24
Closed
michielbdejong wants to merge 2 commits into
Closed
michielbdejong wants to merge 2 commits into
michielbdejong wants to merge 2 commits into
Conversation
The auth/pagination/crud-causality overlays for both OAD subset documents have moved to localthought/overlays (github.com/github-issues/1.1.4 and googleapis.com/google-calendar/v3), merged there in localthought/overlays#145. Left open pending the config/discovery changes needed to load these overlays from their new home instead of spec/*/overlays before merging. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012bmJGaUn2iAazsUGqaL98N
Per CLAUDE.md's NLnet Generative AI disclosure policy. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012bmJGaUn2iAazsUGqaL98N
michielbdejong
added a commit
that referenced
this pull request
Sep 8, 2026
…oring them (#26) github-issues.openapi.yaml, google-calendar.openapi.yaml and their six overlays moved to localthought/openapi-directory (PR #1) and localthought/overlays (PR #145), superseding the file removals proposed in #23/#24. This adds scripts/fetch-oad.sh, which pulls them back into the exact same spec/<platform>/ paths GITHUB_DEFAULTS/GOOGLE_CALENDAR_DEFAULTS already pointed at (pinned by commit), so config.rs needs no path changes. spec/ is now gitignored rather than committed. Verified: fetched bytes are byte-identical to what was removed; cargo test/clippy/fmt and both wasm32 checks pass without running the script (nothing in the suite touches spec/); the built binary, run zero-config against the fetched files, resolves the document, applies all three overlays, derives the ontology and makes a real request to the GitHub API — the README's stand-alone path still works end to end. Claude-Session: https://claude.ai/code/session_012bmJGaUn2iAazsUGqaL98N Co-authored-by: Claude <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
2 participants
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.
Superseded by #26, which does the same removal plus the
scripts/fetch-oad.shfix-up somainstays green (this PR alone would have broken the zero-configcargo runpath).