feat(apollo-react): add case-management trigger node manifest#720
Open
kittyyueli wants to merge 2 commits into
Open
feat(apollo-react): add case-management trigger node manifest#720kittyyueli wants to merge 2 commits into
kittyyueli wants to merge 2 commits into
Conversation
Phase 1 manifest for uipath.case.trigger per Case Unified schema onboarding spec. Triggers only — stage, task, condition, and edge manifests are out of scope here.
- Normalize forbidden target category to 'case-management-trigger' so the trigger manifest is internally consistent. - Add Components/CaseFlow/Trigger story that registers caseFlowManifest through NodeRegistryProvider and renders uipath.case.trigger nodes via BaseNode (uses useCanvasStory + createNode). - Leave the legacy Components/TriggerNode story untouched.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Dependency License Review
License distribution
Excluded packages
|
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
2 participants
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.
Summary
Phase 1 of the Case Unified schema onboarding — adds the
uipath.case.triggermanifest and a Storybook example. Scope is limited to trigger nodes only; stage, exception stage, task, condition, and edge manifests are intentionally deferred.packages/apollo-react/src/canvas/components/CaseFlow/case-flow.manifest.tswith thecase-management-triggercategory, thecaseManagementTriggerManifestnode manifest (single right-side output handle,case-stagetarget whitelist,case-management-trigger/case-conditionblacklist), and the combinedcaseFlowManifestexport — mirroring the shape ofagent-flow.manifest.ts.CaseTrigger.stories.tsx(Storybook titleComponents/CaseFlow/Trigger) that registerscaseFlowManifestviaNodeRegistryProviderand renders manifest-drivenuipath.case.triggernodes throughBaseNode(useCanvasStory+createNode), showcasing execution-status and icon-override variants.Components/TriggerNodestory and theTriggerNodecomponent are untouched.Test plan
Components/CaseFlow/Trigger / Defaultrenders 10 trigger nodes in a 5-column grid in Storybook.InProgress,Completed,Failed,Paused,NotExecuted) display the expected execution-state styling.display.iconoverrides (clock,mail,webhook) replace the manifest's defaultbolticon.case-management-trigger).case-stagesucceeds (verifiable once a stage manifest lands).npx tsc --noEmit -p packages/apollo-react/tsconfig.jsonreports no new errors.Components/TriggerNode / Defaultstory still renders unchanged.https://claude.ai/code/session_0157FiTqLMdaPe7BpZQU1Ktw
Generated by Claude Code