chore: version packages#69
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@perspective-ai/sdk@1.14.0
Minor Changes
fe18680: Replace the loading skeleton with the interview's real chrome.
Instead of a skeleton that mirrors the interview UI's internal layout (welcome
card, message, input pill) — which drifts whenever that UI changes — the
loading state now renders what the interview actually looks like from the
outside in:
{host}/interview/{researchId}/scene-image) behindapp's card treatment), with
with a fading tail over a faint track, tinted with the brand primary
resolved with the SDK's usual precedence: local
brand.primaryoverride →API embed config (
primaryColor/darkPrimaryColor) → Perspectivedefault (
#7c3aed/#a78bfa). As essential loading motion it is notdisabled by
prefers-reduced-motion.The scene image is applied only after it has actually loaded, layered over
the app's default surface color (
#f5f2f0light,#15171edark, or a custombrand.bg) — so a research without a scene (404), a slow network, or ablocked request cleanly degrades to a solid color.
Because the loading state renders in the host page DOM (an overlay sibling of
the cross-origin iframe), responsiveness is driven by CSS container
queries on the slot the consumer provides — not viewport media queries. The
card's sizing mirrors the interview app's own container queries (full-bleed
below 672px width; a centered
max-width: 672pxbox above it, with verticalpadding stepping 4px → 48px → 80px at the app's 448px/768px container-height
breakpoints), so the card doesn't jump at handoff. Breakpoints are in px, not
the app's rem: the overlay lives in the host page, so rem would resolve against
the host's (uncontrolled) root font-size, whereas the card must match the
iframe's fixed pixels.
LoadingOptionsgains optionalresearchIdandhost(used for the sceneURL) and
apiConfig(used for the loader tint); all embed types pass themautomatically.
A new
prefetchSceneImage(researchId, host?)export warms the scene image onintent signals — the SDK wires it to float-bubble hover/focus and to
data-perspective-popup/-slidertrigger elements — so deferred embeds openwith the scene already cached.
@perspective-ai/sdk-react@1.14.0
Patch Changes