Add direct angle controls and restore streamlined exports - #115
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a-baran-orhan
marked this pull request as ready for review
August 1, 2026 14:47
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.
What changed
− / angle / +spinner for authored joint angles, constrained to the shared range-of-motion limits.Why
Authors who are not animators should be able to explore a Posecode movement without already knowing anatomical angle values. This brings Bret Victor-style direct manipulation to the text-first workflow while preserving the source document as the single source of truth.
User impact
Clicking a joint name now identifies it on the 3D figure. Clicking its numeric angle turns the value into an accessible spinner; every change updates the source and re-renders the movement immediately.
The playground also matches the deployed header again: authors see one Export action instead of two competing download buttons, and GitHub opens the project repository rather than issue creation.
Root cause
The streamlined header existed in commit
d5ec0db, but that commit remained onagent/streamline-playground-actionsand never reachedmain. Branches created frommaintherefore restored the older two-button/issue-link UI. This PR carries that commit forward and adds regression coverage.Validation
npm run typechecknpm run buildnpm test -- --run playground/test/playground-actions.test.ts playground/test/direct-manipulation.test.ts playground/test/analytics-wiring.test.ts packages/posecode-render/test/render.test.ts(56 tests passed)45° → 46°updated the live pose