Repository navigation
Conversation
Import the pinned GHCP WhatsApp relay sample and integrate its documentation with the Just the Docs site. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5869ff02-9098-43dc-a19c-4ae824425ac2
| url: "https://lookaside.fbsbx.com/media", mime_type: sample.mime, file_size: sample.bytes.length, | ||
| sha256: createHash("sha256").update(sample.bytes).digest("hex"), | ||
| }); | ||
| if (url.startsWith("https://lookaside.fbsbx.com")) { |
| { file_size: limits.fileBytes + 1 }, { url: "https://untrusted.example.org/file" }, | ||
| { sha256: "0".repeat(64) }, | ||
| ]) { | ||
| const client = new MetaClient(config, async input => String(input).includes("graph.facebook.com") |
Accept supported image, audio, and video files sent as WhatsApp documents while retaining MIME-based limits and validation. Add eight regression tests and document the behavior. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5869ff02-9098-43dc-a19c-4ae824425ac2
| let calls = 0; | ||
| const client = new MetaClient(config, async input => { | ||
| calls++; | ||
| return String(input).includes("graph.facebook.com") ? Response.json({ |
| let calls = 0; | ||
| const client = new MetaClient(config, async input => { | ||
| calls++; | ||
| return String(input).includes("graph.facebook.com") ? Response.json({ |
This branch has not been deployed
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.
Summary
extensibility/agents-sdk/whatsapp-relay/, under Extensibility → Agents SDK → WhatsApp Relay.MemoryStorage, and GHCP conversation state for each sender..env.example. Preserve the approved screenshot, Mermaid flow, documentation order, and detailed enterprise architecture guidance.Source and scope
Import only the 38 tracked files from
WhatsAppRelaySample/atadilei/CopilotStudioSamples@08422ea96c3ca2be680ea6461c22a9ca93f3c3d0. No fork history or repository-root files are imported. All 35 non-Markdown sample files are byte-identical to that snapshot; only the three Markdown documents are adapted, plus one row in the upstream category README.No CI trigger changes, historical migration mapping changes, durable storage, brokers, additional LLMs, or alternate runtimes are included. The existing fork PR and branch are untouched.
Validation performed in the relocated sample
npm test: 97 passed, 0 failed, 0 skipped on Node.js 22.17.0, including TypeScript compilation and setup/deployment regression tests. Dependencies were restored withnpm ciafter the initial missing-TypeScript failure.JEKYLL_ENV=production bundle exec jekyll build: passed on Ruby 3.3.9; existing Just the Docs Sass deprecation warnings remain..env, setup journals, credentials,node_modules,dist,_site,vendor, or validation artifacts are committed.git diff --cached --checkpassed.Limitations and live-test boundary
This import performed no cloud provisioning, authentication changes, Meta callback changes, Azure deployments, or live WhatsApp tests. Setup tests use local fixtures rather than live providers.
The documentation preserves earlier live-test evidence and its limits: one fixed Azure deployment entrypoint exited successfully; a second local entrypoint was interrupted, although its remote deployment completed and the remaining checks passed directly. This is not represented as two uninterrupted CLI successes. Full interactive WhatsApp acceptance, media-modality coverage, and real two-user validation remain unverified. This experimental sample is not an enterprise-ready channel.