Make Microsoft Graph slice URLs first-class spec sources - #1755
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 37ddaa8 | Commit Preview URL Branch Preview URL |
Aug 26 2026, 06:35 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 37ddaa8 | Aug 26 2026, 06:36 AM |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
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.
Follow-up to #1753, removing the source substitution it introduced. The interception meant the stored specUrl claimed Microsoft's monolith while the bytes came from our release assets — an undisclosed supply-chain hop between the claimed source and what integrations actually ingest.
Now the URL is the byte source, always:
files.yaml→ the files preset;default.yaml→ the default bundle), and narrowing within a slice travels visibly in the fragment (default.yaml#preset=mail,calendar).#preset=fragment it still applies the selection filter to the fetched bytes (unchanged, and still memory-fatal in cloud; pasting the monolith URL without a preset match lands in the generic path's size guard with the preset suggestion).Known follow-up: integrations stored before this change carry the bare monolith specUrl, so their refresh path still fetches the monolith (pre-existing behavior); migrating them to their selection's slice URL is a separate one-off.
Verified: full plugin suite (303 tests) including new URL-classification and no-substitution adapter tests;
microsoft-graph-default,microsoft-emulator, andprovider-plugins-uie2e scenarios pass against the live release assets, with the UI scenario asserting the tile now shows the slice URL.