Repository navigation
Retire stale calendar-proxy.patch; document real write-back status - #19
Merged
Merged
Conversation
#5 Phase 1: calendar-proxy.patch no longer applies — integration-proxy moved from a static per-platform providers.rs list to a dynamic OpenAPI+Overlay catalog fetched from localthought/overlays, and the CORS/If-Match forwarding and calendar.events scope it patched in are already generic, already-shipped behavior there. The actual remaining gap was narrower: the composed google-calendar catalog only ever declared GET operations, so no PATCH could reach Google regardless of scope or CORS. That's closed by localthought/overlays#166 (adds a patch operation on an existing event, matching applyCalendarEdit's summary/description/location/start/end fields and If-Match) and localthought/integration-proxy#75 (bumps the deployed catalog pin to it). Both still need merging, and the proxy needs restarting, before any write reaches Google — not done as part of this work. README now points at those PRs instead of the removed patch file.
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.
#5 Phase 1: calendar-proxy.patch no longer applies — integration-proxy moved from a static per-platform providers.rs list to a dynamic OpenAPI+Overlay catalog fetched from localthought/overlays, and the CORS/If-Match forwarding and calendar.events scope it patched in are already generic, already-shipped behavior there.
The actual remaining gap was narrower: the composed google-calendar catalog only ever declared GET operations, so no PATCH could reach Google regardless of scope or CORS. That's closed by
localthought/overlays#166 (adds a patch operation on an existing event, matching applyCalendarEdit's summary/description/location/start/end fields and If-Match) and localthought/integration-proxy#75 (bumps the deployed catalog pin to it). Both still need merging, and the proxy needs restarting, before any write reaches Google — not done as part of this work. README now points at those PRs instead of the removed patch file.