Repository navigation
fix(figma): use selected Audiences and separate comment setup from import - #56
Merged
Merged
Conversation
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
1 participant
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.
The Figma plugin should ask for a question and selected Audiences. Its main picker now uses the published Minds Audience grid, the existing Select Audiences translation, and the selected Audience count. Connecting fetches only the first Audience page; individual Mind endpoints remain available to existing clients.
Comment setup is explicitly separate from whole-board import: the plugin exports the selected frame directly and uses the board link solely to identify the native-comment destination. The comment authorization URL retains its independent
figma-commentspurpose. Public Figma plugins cannot accessfigma.fileKey; this change does not claim automatic file identity or live comment delivery before the companion backend is released.Validation: full repository checks passed on retry (the first run hit the existing Slack HTTP lifecycle timing assertion); generated-UI Chromium Audience selection, count, missing-link recovery, confirmation and completed-result delivery contracts passed. Browser API/provider responses are fixtures. The updated native bundle is installed on Alexander’s Mac with a backup.