studio: connections panel, binding editor and live values
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #163 by @dezlitz — merged
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start in apps/studio and read the Studio shell PR (holodeck#16), then trace the provider contributions, ProviderContext, and the inspector and ProcessEditor entry points. The issue groups several substantial pieces of work, so check the E2 issue for the camera-props dependency before choosing a piece. Done means the connections panel, binding editor, live metrics wiring, and camera persistence wiring described here are implemented.
Written by the indexing model from the issue text.
Description
Follow-up to the Studio shell PR (holodeck#16, lane S1). Still to build in apps/studio:
- Connections panel: list/add/remove
ProviderConnections on the document envelope (provider picker from installedholodeck.providercontributions, non-secretconfigform via TanStack Form). Secrets insessionStorageonly, supplied throughProviderContext.secret. - Binding editor in the inspector: per param,
{ connection, source, transform }; source picker via the provider'sbrowse; transform editor (scale / threshold / map / format, validated withvalidateTransform). - Live values:
host.createProviderHub()+connectIsoDocument/useHubMetricsintoProcessEditormetrics. - Camera persistence wiring once
ProcessEditorhas camera props (see the E2 issue).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 10h 39m
- Merged PRs (30d)
- 38
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperdrive-technology/holodeck
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hyperdrive-technology/holodeck#196 ·
Maintainers usually reply within 1 day
-
area:docs review-finding
Difficulty 1/5 Under an hour Newbie friendliness 70/100
hyperdrive-technology/holodeck#180 ·
Maintainers usually reply within 1 day
-
Flaky E3 test: native cut with no keydown (holodeck#123) in editing-ux-render.test.tsPossibly taken @dezlitz claimed this today. Openarea:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hyperdrive-technology/holodeck#141 ·
Maintainers usually reply within 1 day
-
assetUrlProblem: data:image check uses the un-normalised URL, so ' data:image/png...' is rejectedOpenarea:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hyperdrive-technology/holodeck#104 ·
Maintainers usually reply within 1 day
-
agent area:holodeck good first issue priority:p2
Difficulty 1/5 Under an hour Newbie friendliness 72/100
hyperdrive-technology/holodeck#64 ·
Maintainers usually reply within 1 day
All issues in hyperdrive-technology/holodeck
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
paperclipai/paperclip#16785 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
code-yeongyu/senpi#3661 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#32731 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
mastra-ai/mastra#27538 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Yeachan-Heo/oh-my-codex#3822 ·
Maintainers usually reply within 1 day