FE-1500: add editor presentation profiles - #9425
Draft
kube wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
kube
force-pushed
the
claude/fe-1500-presentation
branch
from
August 29, 2026 20:03
4266f7b to
bc5f034
Compare
kube
force-pushed
the
codex/fe-1500-router
branch
from
August 29, 2026 20:03
ad4e76a to
2302d43
Compare
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 is the purpose of this PR?
Adds a
presentationProfileprop toPetrinaut(editororreview) that gates authoring-only controls, and extracts scenario and playback controls into shared components so later surfaces can compose them outside the full editor. Stacked on #9359.🔗 Related links
🔍 What does this change?
PetrinautPresentationProvidercontext maps a profile to capability booleans (showMutationActions,showSourceCode,showCustomVisualizers,showViewportSettings,showMinimap,compactControls). The defaulteditorprofile keeps every capability on, so existing hosts are unchanged;reviewsuppresses authoring actions for read-only pages.SelectedItemPropertiesfromPropertiesPanel/panel.tsx,SimulationScenarioControlsandsimulation-parameter-boundsfromsimulation-settings.tsx, and a compact variant of the bottom-barSimulationControlsandPlaybackSettingsMenu(with anallowedSpeedsallow-list).React.lazyboundaries (createDeferredSubView).Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR:
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR:
🛡 What tests cover this?
simulation-parameter-bounds.test.ts.@hashintel/petrinautunit suite runs the editor with the default profile.❓ How to test this?
yarn workspace @hashintel/petrinaut dev.<Petrinaut presentationProfile="review" />in a host and confirm add/delete/rename affordances and source-code fields are hidden.